Hello, is it possible to bypass the default activation module and use keypairs generated on the CI-server to establish trust between authoring & public instances?
The optimal workflow from our point of view would be to produce .war files that are deployable without change to both authoring & public instances. The authoring & public instances are 2 physically different instances. Deployment should be one-click executable from Jenkins. Right now such a scenario seems to be impossible as new deployments initiate regeneration of keypairs and every deployment would require a developer's / admin's involvement. To illustrate the situation a bit better the optimal workflow would consist of 4 stages: 1) development 2) integration server, on installation the database is dropped and content is synchronized from authoring 3) authoring server, on installation the new version of the war file is deployed (through Jenkins) nut the database is kept intact 4) public server, same as authoring server. The publishing trust between authoring & public server should persist after new deployments. Best, V. -- Context is everything: http://forum.magnolia-cms.com/forum/thread.html?threadId=726601e1-8019-41e7-91d9-dd0242387d63 ---------------------------------------------------------------- For list details, see http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
