I am working in a magnolia project where the workspaces have been split in 3 repositories one for contents, one for users data, and another for configuration data. The repositories are saved on the file system in 3 different folders, content, users and conf. However between deploys we change the configuration (mostly of our modules) often, and in order to re-install all the modules again we delete the folder config and it triggers an install for all the modules (and all the bootstrap xml files in the modules are loaded again), and we do not lose any content.
But it is giving me a big problem, unless I delete all the workspaces, the server specific configuration is ignored by cms (https://documentation.magnolia-cms.com/display/DOCS/Configuration+management), all the configuration files in magnolia.bootstrap.dir are ignored, while I need to load the server specific configuration every time when I delete the config workspace. How can it be achievable? For example, I have different subscribers for the activation in different environments, and when I delete the configuration the list of subscribers become the default one with only "magnolia8080" instead of loading the bootstrap file inside magnolia.bootstrap.dir . -- Context is everything: http://forum.magnolia-cms.com/forum/thread.html?threadId=c618ac36-f4b6-4eba-a97f-d21f9184d141 ---------------------------------------------------------------- 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: <user-list-unsubscr...@magnolia-cms.com> ----------------------------------------------------------------
