Re: [otrs] Deploy OTRS configuration from test environment to production environment
Hi guys, Thank you so much. But I think I wasn't clear enough. Imagine I already have two environments, both operational and identical at time zero: one for testing and one for production. Every time a request for change OTRS configuration arrives (some new configuration, a new dynamic field, a new ACL, new process, everything about configuration etc), I need to implement it, test it and then deploy it to production, like any other application. In other words, I need to export/import all configuration data on a regular basis, but should leave the other production data intact (history of tickets, articles etc...). So drop the database is not an option. Any idea? Thanks
Hello Samuel, The best way we've found to that is as follow. 1. Take into account that you have data tables and config tables. Data tables are the ones you just mentioned and config tables are tables like group, user, role, group-role, and so on. 2. When you work on development (test) systems, you need to know where the changes are applied so you can move them to the production system when needed. Config is mantained in ZZZAuto files and you can move that from one server to another. 3. Backup and update individual tables when you need to pass changes (dynamic fields, permissions, groups, roles, etc) 4. Never move or update data tables (ticket, article, faq,dynamic_field_value). 5. Processes, ACLs and stats you can export and import, but need to have config data first (dynamic Fields, Process Configuration) We have not found a better way of doing so, you just need to be sure your systems are kept syncronized after a pass to production. Regards 2015-08-13 6:33 GMT-06:00 Samuel Diniz Casimiro < samuel.casimiro@camara.leg.br>:
Hi guys,
Thank you so much. But I think I wasn't clear enough.
Imagine I already have two environments, both operational and identical at time zero: one for testing and one for production.
Every time a request for change OTRS configuration arrives (some new configuration, a new dynamic field, a new ACL, new process, everything about configuration etc), I need to implement it, test it and then deploy it to production, like any other application.
In other words, I need to export/import all configuration data on a regular basis, but should leave the other production data intact (history of tickets, articles etc...). So drop the database is not an option.
Any idea?
Thanks
--------------------------------------------------------------------- OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs
-- *Alvaro Cordero RetanaConsultor de Tecnologias* *Tel: 22585757 ext 123* *Email:* alvaro@gridshield.net
participants (2)
-
Alvaro Cordero -
Samuel Diniz Casimiro