Upgrading is not hard, we are just trying to save you the pain if something goes wrong.
The easiest way to upgrade is to download the code, unzip it over your current production code. However if something breaks there is going to be no easy way to revert. I have shown my designer to use git in under and hour so I am sure a programmer can learn it in a half hour :D No offence but every serious project should be put under version control, this will save you in many ways if something goes wrong. IE: Your production server goes down, your development computer's hard drive fries and you don't have an up-to-date back-up etc.. On Mon, Mar 12, 2012 at 4:38 PM, horridohobbyist <horrido.hobb...@gmail.com>wrote: > You guys are kidding, right? I have to use source code control or Git or > Fabric (none of which I'm familiar with), just to update my > *production*system? I have to spend time and energy to learn all these tools > (which I > no longer need for development)? > > In all other respects, web2py is easy...writing a web2py application is > easy...deploying it is easy...but *updating* it requires jumping through > all these hoops? Please tell me that this is a sick joke. > > > On Monday, 12 March 2012 19:19:49 UTC-4, Detectedstealth wrote: >> >> http://newtriks.com/2011/12/**01/automated-deployment-using-**git/<http://newtriks.com/2011/12/01/automated-deployment-using-git/> >> >> On Mon, Mar 12, 2012 at 4:17 PM, Bruce Wade <bruce.w...@gmail.com> wrote: >> >>> 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/<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://ca.linkedin.com/in/brucelwade> >>> http://www.wadecybertech.com >>> http://www.warplydesigned.com >>> http://www.**fitnessfriendsfinder.com<http://www.fitnessfriendsfinder.com> >>> >> >> >> >> -- >> -- >> Regards, >> Bruce Wade >> http://ca.linkedin.com/in/**brucelwade<http://ca.linkedin.com/in/brucelwade> >> http://www.wadecybertech.com >> http://www.warplydesigned.com >> http://www.**fitnessfriendsfinder.com<http://www.fitnessfriendsfinder.com> >> > -- -- Regards, Bruce Wade http://ca.linkedin.com/in/brucelwade http://www.wadecybertech.com http://www.warplydesigned.com http://www.fitnessfriendsfinder.com
