[MAGNOLIA-6307] Server specific configuration ignored Created: 24/Jun/15  Updated: 19/May/22  Resolved: 19/May/22

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Daniele Biagi Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

tomcat 7 / java 7 / Windows Server 2008 and CentOS 6.6


Attachments: XML File repositories.xml    
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:
Visible to:
Daniele Biagi, Enrico Cammarota, Sandra Dziedzic

 Description   

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 .



 Comments   
Comment by Roman Kovařík [ 19/May/22 ]

Hello,

This ticket is now marked as closed due to one of the following reasons:

  • A long period of inactivity
  • Uses an old or Beta version of an application, module, or framework that we no longer support
  • The issue is no longer reproducible or has been fixed in later versions

If you are still facing a problem or consider this issue still relevant, please feel free to re-open the ticket and we will reach out to you.

Thank you,
The Magnolia Team

Generated at Mon Feb 12 04:13:16 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.