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
-----Original Message-----
From: otrs-bounces@otrs.org [mailto:otrs-bounces@otrs.org] On Behalf Of otrs-request@otrs.org
Sent: Wednesday, August 12, 2015 5:37 PM
To: otrs@otrs.org
Subject: otrs Digest, Vol 83, Issue 3
Send otrs mailing list submissions to
otrs@otrs.org
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.otrs.org/cgi-bin/listinfo/otrs
or, via email, send a message with subject or body 'help' to
otrs-request@otrs.org
You can reach the person managing the list at
otrs-owner@otrs.org
When replying, please edit your Subject line so it is more specific than "Re: Contents of otrs digest..."
Today's Topics:
1. Deploy OTRS configuration from test environment to
production environment (Samuel Diniz Casimiro)
2. Re: Deploy OTRS configuration from test environment to
production environment (Leonardo Certuche)
3. Re: Deploy OTRS configuration from test environment to
production environment (Jay)
4. Re: Deploy OTRS configuration from test environment to
production environment (Jay)
----------------------------------------------------------------------
Message: 1
Date: Wed, 12 Aug 2015 19:53:36 +0000
From: Samuel Diniz Casimiro