I don't know whether it is the best way but I use mercurial for my apps. That helps to go back to an earlier version of a file when something go wrong.
Regards Johann On 5 November 2013 07:34, Jayadevan M <[email protected]> wrote: > Let me try rephrasing the question. What is the preferred way of deploying > changes in production? > > On Thursday, October 3, 2013 6:15:44 PM UTC+5:30, Jayadevan M wrote: >> >> I have deployed version 1 of an application in production. Let us say we >> used the admin console and created a project (.w2p) file and that was how >> we deployed it. Which is the best way to roll out the next release? If we >> use the same approach, it will also move to prod the files under databases >> folder and result in conflicts? >> > -- > Resources: > - http://web2py.com > - http://web2py.com/book (Documentation) > - http://github.com/web2py/web2py (Source code) > - https://code.google.com/p/web2py/issues/list (Report Issues) > --- > You received this message because you are subscribed to the Google Groups > "web2py-users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > -- Because experiencing your loyal love is better than life itself, my lips will praise you. (Psalm 63:3) -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
