pauldix

require 'feedzirra'

# fetching a single feed
feed = Feedzirra::Feed.fetch_and_parse("http://feeds.feedburner.com/PaulDixExplainsNothing")

# feed and entries accessors
feed.title          # => "Paul Dix Explains Nothing"
feed.url            # => "http://www.pauldix.net"
feed.feed_url       # => "http://feeds.feedburner.com/PaulDixExplainsNothing"
feed.etag           # => "GunxqnEP4NeYhrqq9TyVKTuDnh0"

perezd

require 'rubygems'
require 'activerecord'

ActiveRecord::Base.establish_connection(
    :adapter => 'mysql',
    :host => 'localhost',
    :username => 'root',
    :database => 'craigslist'
)

bmizerany

require 'sinatra/base'

run Sinatra.new {
  get('/') do
    content_type "text/plain" # you can also use Rack::ContentType
                              # with Sinatra except here we want
                              # more control since Sinatra gives it
                              # to us.  Rack::ContentType sets the
                              # Content-Type on every route/url for
                              # the current mapping.

brandondrew

#!/bin/bash
###########################################################
# TRIBUNE-SPECIFIC BUILD HOME script:
# This script sets up your home directory fast with basic 
# necessities and amenities, to give you sanity when you
# work on a Unix box where you don't have root access.
###########################################################
# TO USE:
# curl https://raw.github.com/gist/259348/build_home.sh | bash
# OR:

karmi

What's wrong with Ruby libraries for CouchDB?

During the last year, I have worked on couple of Ruby/Rails based projects where the primary datastore was CouchDB. CouchDB, to me, is a dream database for web developer come true. The simplicity, the HTTP-based API, the abandonment of SQL semantics, the inspiring community, that all reminds me of when I came into Rails years ago.

However, working with Couch in Ruby and Rails is very, very painful, in my opinion. I'd like to briefly summarize some of my frustrations here. Maybe they are shared, maybe not -- if they are, I think we should launch some coordinate effort to make using Couch in Ruby a pleasure and intelectual satisfaction, not endless loops of research and hacks to „make it work“.

Please note, that my interest is solely to stir the debate. I may be severely mistaken in any point. But, I'd like using Couch in a Ruby application to be a joy, not a frustration, which is what I've met more times than I'd ha

dhh

describe "GET current" do
    before do
      @request.cookies['hidden_notices'] = "1,#{notices(:permanent).id}"
      get :current, :format => 'js'
    end

    it { should respond_with(:success) }
    it { should set_cookie(:hidden_notices).to("#{notices(:permanent).id}") }
    it { should render_template('notices/current') }
  end

schacon

class Stopwatch

  attr_writer :splits, :max, :start, :end, :total

  def initialize(message)
    @message = message
    @splits = []
    @max = 5
  end

ianmurrays

set :test_log, "logs/capistrano.test.log"

namespace :deploy do
  before 'deploy:update_code' do
    puts "--> Running tests, please wait ..."
    unless system "bundle exec rake > #{test_log} 2>&1" #' > /dev/null'
      puts "--> Tests failed. Run `cat #{test_log}` to see what went wrong."
      exit
    else      
      puts "--> Tests passed"

clintel

Fenced code blocks inside ordered and unordered lists

1. This is a numbered list.

2. I'm going to include a fenced code block as part of this bullet:

   Code
   More Code
   

brandondrew

Just a informational gist if you plan to install "beanstalkd" via MacPorts and get a compiler error:

:info:build net.c: In function 'make_server_socket':
:info:build net.c:35: warning: 'fd' may be used uninitialized in this function
:info:build make[1]: *** [net.o] Error 1
:info:build make[1]: *** Waiting for unfinished jobs....

This is a known issue within the "net.c" file. I've found a diff[1] for said file on the web and applied it locally which then allowed me to install the port without problems.

If your install fails like: