If you use GIT you could also automate the entire process. You can write a plugin that will cause your production to change branch and pull the new code for testing whenever you update the target branch on your local host and push.
OK writing the script is a little more complicated then using web2py but it can be done. You might also want to take a look at this: http://jeffkreeftmeijer.com/2010/why-arent-you-using-git-flow/ On Mon, Mar 12, 2012 at 4:00 PM, pbreit <pbreitenb...@gmail.com> wrote: > I definitely suggest using version control instead. SSH in to your server > and "hg clone" web2py from Google Code. Then whenever you want to do an > update, SSH in to server and "hg pull; hg update". You can "hg update" to > specific changesets (ie, roll back if something broke)(this is not fool > proof since there are occasionally changes that make it hard or impossible > to go back). > > I then started using Fabric which makes it a bit easier by not needing to > SSH in to the server and you can set up multi-step tasks to execute > uniformly. > > I do pretty much the same thing with my apps which are hosted at Bitbucket. > > At some point I might start creating new directories with clean new code > and then switching via symbolic links. But my current scheme works fine and > is easy. > -- -- Regards, Bruce Wade http://ca.linkedin.com/in/brucelwade http://www.wadecybertech.com http://www.warplydesigned.com http://www.fitnessfriendsfinder.com
