Hope this helps.

You said "we." That means you really need to use a version control system 
with a branch identical to your production system code. Do all your bug 
fixes against that branch. Whether you do a full regression test before 
pushing new code to the production machine is a judgement call. If you have 
just shot a bug in a single controller or view maybe not. If you've changed 
a module or some other shared file, you should probably regression test the 
whole app.

Your VCS ignore file should include the session, database and error 
directories, and any directories where you store uploaded user files.

Changes to a model are never incremental in my view. Once I have released 
an app into production I never allow any framework to migrate tables. I 
always write my own migration scripts. To introduce the changes, therefore, 
I have to briefly kill the app, run my migration scripts, update the code, 
set fake_migrate to true and restart the app. I also then exercise the app 
enough to ensure the fake migrations take place, set migrate back to False 
and return the app to the users.

I have also made a habit of cleaning the production apps before the upgrade 
and making a tarball of the entire web2py directory. I maintain my own 
rollback directory on the production machine, whether there is a VCS in 
play or not.

I don't necessarily use a VCS on solo projects.

On Tuesday, November 5, 2013 12:34:10 AM UTC-5, Jayadevan M 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.

Reply via email to