Managing Rails versions with Capistrano
18 January 2007 —
1-minute read
The simplest way to deploy your application and tie that release to a specific Rails version is to put Rails in your vendor directory as an svn:external dependency. That’s fine, but it’s not very efficient, and Mike Clark has posted an excellent writeup of the alternatives. If you’ve been wondering if there is a better way, you could do a lot worse than to read what he’s got to say.
Good stuff, Mike!
Reader Comments
Why not use piston?
http://piston.rubyforge.org/
19 Jan 2007
Martin, I’m not sure I understand how piston would help in this scenario. The idea that Mike was pursuing was avoiding putting an entire copy of rails in vendor at all, and using symlinks on the production servers to point to a “shared” Rails checkout.
19 Jan 2007