Kalivo.com - How To: Add gem requirements to a Rails project

Top Authors

Author	#
	185
	148
Anonymous User	49
	28
Kimberly Hieber	27
	23

Note: some conversations may be proxied or secured, thereby causing # differences

Recent

kalivo database import Issue

Akif - 2009-01-06 06:32 PM

The latest database backup files are located at /var/www/apps/kaliv/database_backups. If during the import process the ... read more
New Cap Task: hotfix

terry - 2008-12-09 07:58 PM

I've introduced a new task for the hub cap script, hotfix. It doesn't do all ... read more
(Top...) (More...)

Most Active

Bookmarklet (10 replies)
Kalivo 101 (8 replies)
(Top...) (More...)

« For anyone who uses vim | Home | Proposed change for provision service interface »

How To: Add gem requirements to a Rails project
by terry on 2008-10-22 04:28 PM read 166 times

Old (and busted) way of adding gems to a project:

install gem locally, put note in doc/README for version to give a note to deployer to install gem, and ask terry to install a specific gem on CI.

New way of adding gems, thanks to everybody being >Rails2:

In your config/environment.rb, you'll see a few lines in the Rails::Initializer.run block that start with "config.gem". This is where you add your gem dependencies. After adding a gem here, a deployer (or our cap deploy script), can just run "rake gems:install" and Rails will ensure the dependencies are met.

A few gotchas:

Be sure to list the version of the gem you want, because new gems come out all the time and don't guarantee backwards compatibility.
If you installed from a source like github, be sure to include the source for the gem.
If the main lib file on the gem is not eponymous, you need to add a lib argument that specifies the file to include. Example: rubyntlm, where the main include file is "net/ntlm"