This repository is private.
All pages are served over SSL and all pushing and pulling is done over SSH.
No one may fork, clone, or view it unless they are added as a member.
Every repository with this icon (
) is private.
Every repository with this icon (
This repository is public.
Anyone may fork, clone, or view it.
Every repository with this icon (
) is public.
Every repository with this icon (
| name | age | message | |
|---|---|---|---|
| |
MIT-LICENSE | Wed Apr 16 01:50:20 -0700 2008 | [duff] |
| |
README | Thu Apr 17 11:46:03 -0700 2008 | [duff] |
| |
install.rb | Wed Apr 16 01:50:20 -0700 2008 | [duff] |
| |
lib/ | Thu Apr 17 11:39:36 -0700 2008 | [duff] |
| |
recipes/ | Wed Apr 16 01:50:20 -0700 2008 | [duff] |
README
CadillacEdgeDeploy ================== Is your deployed rails application frozen to a particular revision? If so, when a new version of rails is released how easy is it for you to upgrade? Are you living on the edge of rails? If so, how do you move to a more recent revision when you notice an enhancement you want to take advantage of? Switching to a different version of rails should be easy. Mike Clark described a number of ways to manage your rails versions in this blog post: http://clarkware.com/cgi/blosxom/2007/01/18#ManagingVersionsWithCap Mike wrote of a "Cadillac Approach" in referring to Rick Olson's code that makes managing rails versions quite cinchy. This plugin is basically a rip-off of that blog post and Rick's code. I refactored things a bit primarily because I needed the approach to work even if Rails wasn't installed on the server I was deploying to. I've also changed it since to work with git rather than svn. Example ======= To use the plugin, all you need to do is add the following to your deploy.rb: set :rails_revision, '745359a49452da34978724144eaa318b8a363e08' When you'd like the server to start using a different revision of rails, just adjust the rails_revision variable in your deploy.rb. Copyright (c) 2007 Duff OMelia, released under the MIT license




