Hi Axel 2017-05-30 12:00 GMT+02:00 Axel Braun <[email protected]>:
> > I'm a fan of using packages procided from your distribution for running a > production environment. Local extentions can ba applied to a separate RPM and > installed / updated to production once sufficiently tested. in this case what does your update procedure look like ? your updated specific RPM depends on the Trytond official packages, then - stop Trytond - save databases - update the code with RPM - update every database - restart in production (and cross fingers ?) my questions are : - what is the roll-back procedure in case some problems appear at any step ? - is there a dry-run possibility without stopping production ? - do you know about real production cases where this kind of update is proven ? ( gnu-health ?) regards -- 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/CAHZrxK4-Vyv1%3D_Wwa5wa0QA%3DRu1b0fTJ-deS5ML7WMgnbm7Nxg%40mail.gmail.com.
