El 30/05/17 a les 12:21, Dominique Chabord ha escrit:
my questions are :
- what is the roll-back procedure in case some problems appear at any step ?
If you are using a new virtualenv just have a backup of your database
and you have it. If everything does not go well, restore the backup and
use the previous version code.
- is there a dry-run possibility without stopping production ?
It's possible but when you run the database upgrade you may get blocked
with existing transactions, especially when modifying the structure of a
table used by a lots of users. The procedure will be:
1. Deploy the new version code:
2. Upgrade the database structure while not stopping the previous
server. (Here is when bad things can happen)
3. Stop the old server and start the new one.
--
Sergi Almacellas Abellana
www.koolpi.com
Twitter: @pokoli_srk
--
You received this message because you are subscribed to the Google Groups
"tryton" group.
To view this discussion on the web visit
https://groups.google.com/d/msgid/tryton/2aed6a22-5891-d7e5-d254-7c13315680ad%40koolpi.com.
