Hi, Note that you can achieve the same thing with only one repository, deleting only the workspaces within.
However, the system basically doesn't support what you are doing... I think what you want is just to delete the module configurations of your modules, not the whole config workspace. For example, you could make a small utility module that you include during development, and which looks for a flag set in JCR or on the file-system, and if present, it deletes all the content belonging to your modules... Regards from Vienna, Richard > -----Ursprüngliche Nachricht----- > Von: user-list-ow...@magnolia-cms.com [mailto:user-list-owner@magnolia- > cms.com] Im Auftrag von Daniele Biagi (via Magnolia Forums) > Gesendet: Dienstag, 30. Juni 2015 11:20 > An: Magnolia User List > Betreff: [magnolia-user] Server specific configuration ignored > > 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> > ---------------------------------------------------------------- ---------------------------------------------------------------- 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> ----------------------------------------------------------------
