devdatta

.DS_Store
*.csv
*.pdf

devdatta

Rails 2.3.5 on App Engine (DataMapper)¶ ↑

We assumed Rails 2 would never work without rubygems, and we committed to gem bunlder for JRuby on App Engine, so we were waiting for Rails 3. Fortunately, Takeru Sasaki was able to patch the Rails 2.3.5 calls to rubygems, and now we have it working. Rails 2.3.5 currently spins up several seconds faster than Rails 3, and just a few seconds behind Sinatra.

See the TinyDS version also: gist.github.com/269075

Install the Development Environment¶ ↑

The gems for the development environment include a pre-release appengine-tools gem that provides a pre-release version of jruby-rack.

sudo gem install google-appengine

devdatta

# These commands will help you setup the Rails test environment without problems
#
# MAKE SURE YOU HAVE VIRTUAL BOX INSTALLED http://www.virtualbox.org/wiki/Downloads
#
# Copy paste all of following commands in your normal terminal and the following things will happen:
#  - rails_test_box dir is created
#  - rails master branch is checkout in the dir rails
#  - A Gemfile is created and all the gems to run the virtualbox are installed using bundler
#  - The rails vagrant box is downloaded and added to your vagrant boxes
#  - A Vagrantfile is created for vagrant

devdatta

~/projects/jruby ➔ cat blah.rb
# hello_world.rb
require 'rubygems'
require 'sinatra'

get '/' do
  sleep 2
  "Hello world, it's #{Time.now} at the server!"
end

devdatta

set :application, "example.com"
set :deploy_to, "/var/www/#{application}"

role :app, "example.com"
role :web, "example.com"
role :db,  "example.com", :primary => true

set :scm, :git
set :repository, "ssh://shay@example.com/git/example.com"
set :branch,     "origin/master"

devdatta

# you'd obviously have more settings somewhere
set :scm,        :git
set :repository, "git@github.com:defunkt/github.git"
set :branch,     "origin/master"
set :migrate_target, :current

set(:latest_release)  { fetch(:current_path) }
set(:release_path)    { fetch(:current_path) }
set(:current_release) { fetch(:current_path) }

devdatta

# If your workers are inactive for a long period of time, they'll lose
# their MySQL connection.
#
# This hack ensures we re-connect whenever a connection is
# lost. Because, really. why not?
#
# Stick this in RAILS_ROOT/config/initializers/connection_fix.rb (or somewhere similar)
#
# From:
#   http://coderrr.wordpress.com/2009/01/08/activerecord-threading-issues-and-resolutions/

devdatta

# Removing libraries, and specifying plugins
config.frameworks -= [:action_controller, :action_view, :action_mailer, :active_resource]
config.plugins = [:acts_as_state_machine, :masochism, :resque]

devdatta

Resque.after_fork do |job|
  # How many jobs should we process in each fork?
  jobs_per_fork = [ ENV['JOBS_PER_FORK'].to_i, 1 ].max

  # Set hook to nil to prevent running this hook over
  # and over while processing more jobs in this fork.
  Resque.after_fork = nil

  # Make sure we process jobs in the right order.
  job.worker.process(job)

devdatta

(This is the text of the keynote I gave at Startup Riot 2009. Will update when video becomes available.)

Hi everyone, I’m Chris Wanstrath, and I’m one of the co-founders of GitHub.

GitHub, if you haven’t heard of it, has been described as “Facebook for developers.” Which is great when talking about GitHub as a website, but not so great when describing GitHub as a business. In fact, I think we’re the polar opposite of Facebook as a business: we’re small, never took investment, and actually make money. Some have even called us successful.

Which I’ve always wondered about. Success is very vague, right? Probably even relative. How do you define it?

After thinking for a while I came up with two criteria. The first is profitability. We employ four people full time, one person part time, have thousands of paying customers, and are still growing. In fact, our rate of growth is increasing – which means January was our best month so far, and February is looking pretty damn good.