On Fri, Feb 11, 2011 at 11:35 AM, Ben Hoskings <b...@hoskings.net> wrote: > One reason some prefer to have versioned directories + a symlink is to store > deploy history and enable easy rollbacks. > I use a deploy branch that I merge into using --no-ff (i.e. don't fast > forward, always create a merge commit) before each deploy. This provides the > same history, and has the advantage that since it's git commit history, it's > immutable—there's no question about what was deployed when, and the history > is backed up everywhere. > Rolling back just means resetting to a previous merge commit on that branch.
Right, the history is always there, but you're not concerned about a git merge/reset not being as instant as a symlink change? > If the previous version won't run on the migrated DB, or vice versa, then > you need to take the app offline. So for bigger apps that can't go offline, is the only solution to work around it and avoid doing those kinds of migrations? On Fri, Feb 11, 2011 at 12:25 PM, Mike Bailey <m...@bailey.net.au> wrote: > That's the main job of net-ssh. :-) > The main job of Capistrano is to allow you to define roles and tasks. > ... > You're manually triggering a deploy by doing a git push to the target > server. It's not an unattended install by any stretch. Right. :-) On Fri, Feb 11, 2011 at 12:29 PM, Ben Hoskings <b...@hoskings.net> wrote: > On Friday, 11 February 2011 at 3:25 PM, Mike Bailey wrote: >> I'd love to see something really simple that will take care of holding page, >> bundler, migrations, app_restart and the like. I just don't need it enough >> to write it myself. :-) > > Workin' on it :) Cool! -- You received this message because you are subscribed to the Google Groups "Ruby or Rails Oceania" group. To post to this group, send email to rails-oceania@googlegroups.com. To unsubscribe from this group, send email to rails-oceania+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rails-oceania?hl=en.
