@Julio: Thanks, I think I won't use git-deploy directly, but it does > look interesting. > What I'm really wondering about is: > > - Updating files in one live copy of the app vs. version directories > and a symlink. 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. > - Running migrations to a schema the old (current) code can't work with. > If the previous version won't run on the migrated DB, or vice versa, then you need to take the app offline. The deploy system I'm working on puts up an nginx-rewritten maintenance page up for that part of the deploy. —Ben -- 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 [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rails-oceania?hl=en.
