Don't go updating files in one live version of the app ... it's a recipe for disaster.
By having releases and symlinking you gain a nice history of your application through deployments, and if you deploy a broken version then you can easily roll back, either to the old directory in the case of capistrano deployments, or to the old revision in the case of git push deployments. This is really a better wayt to go. As for migrations, they run in the version currently being deployed, so the code has been copied up, then a rake task for the db migrate runs (loading this new version of the code) and once it is successful the running server is restarted and loads this version of the code with the new schema. On Friday, 11 February 2011 at 2:27 PM, Chris Berkhout wrote: @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. > - Running migrations to a schema the old (current) code can't work with. > > @Ben & @Ryan: Sounds good. I look forward to reading them! > > Cheers, > Chris > > > On Fri, Feb 11, 2011 at 6:52 AM, Ryan Bigg <radarliste...@gmail.com> wrote: > > I'm working on an Ubuntu 10.10 single-app deployment guide now, should be > > done next week some time. > > > > > > > > On 11/02/2011, at 9:39, Ben Hoskings <b...@hoskings.net> wrote: > > > > On 10 February 2011 23:14, Chris Berkhout <chrisberkh...@gmail.com> wrote: > > > > > > Hi All, > > > > > > I'm trying to improve my setup for deploying to a VPS and have run > > > into a few questions. > > > > > > The general idea is to be able to do a git push to an account on the > > > VPS and have git hooks do anything necessary on the server side to > > > redeploy. > > > > I'm working on just this at the moment. Write-up on the way. > > —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 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. > > > > -- > > 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. > > -- > 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. > -- 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.
