Nathan Fixler fixlr

github

https://github.com/search?q={query}

grooveshark

http://grooveshark.com/#/search?q={query}

A Common .ruby-version File For Ruby Projects

Background

I've been using this technique in most of my Ruby projects lately where Ruby versions are required:

Create .rbenv-version containing the target Ruby using a definition name defined in ruby-build (example below). These strings are a proper subset of RVM Ruby string names so far...
Create .rvmrc (with rvm --create --rvmrc "1.9.3@myapp") and edit the environment_id= line to fetch the Ruby version from .rbenv-version (example below).

Today I learned about another Ruby manager, rbfu, where the author is using a similar technique with .rbfu-version.

Zero downtime deploys with unicorn + nginx + runit + rvm + chef

Below are the actual files we use in one of our latest production applications at Agora Games to achieve zero downtime deploys with unicorn. You've probably already read the GitHub blog post on Unicorn and would like to try zero downtime deploys for your application. I hope these files and notes help. I am happy to update these files or these notes if there are comments/questions. YMMV (of course).

Other application notes:

Our application uses MongoDB, so we don't have database migrations to worry about as with MySQL or postgresql. That does not mean that we won't have to worry about issues with the database with indexes being built in MongoDB or what have you.
We use capistrano for deployment.

Salient points for each file:

This song is Copyrighted in U.S., under Seal of Copyright # 154085, for a period of 28 years, and anybody caught singin it without our permission, will be mighty good friends of ourn, cause we don’t give a dern. Publish it. Write it. Sing it. Swing to it. Yodel it. We wrote it, that’s all we wanted to do.

Woody Guthrie, 1940's —

	http://www.youtube.com/watch?v=HP4HiZt3DFE

	path
	appnexus
	taskrabbit
	singleplatform
	birchbox
	xobni
	jelli
	memsql

	# Ship it! rake task
	#
	# Merge branch (master by default) to deployment branch, and deploy to server.
	#
	# Prerequisite:
	#
	# * Declare all deployment branches in `ALL_DEPLOYMENT_BRANCHES`
	# * Declare deploy only branches in `DEPLOY_ONLY_BRANCHES` (ie, does not merge master)
	# * Modify `Deploy.command` function as necessary
	#