[MAGNOLIA-7882] Enable different configuration for publics and authors Created: 23/Jul/20 Updated: 21/Apr/22 |
|
| Status: | Accepted |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Story | Priority: | Neutral |
| Reporter: | David Lopez | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| 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)
|
||||||||||||||||
| Description |
|
As a developer, I want to be able to provide configuration to just the author or the public, so that I can handle the different needs of the different systems. Currently when a developer provides yaml configuration in a light module, it is typically applied to both the author and the public instances. But sometimes there is configuration that should only be supplied to one system or the other, for example a virtualURI mapping. While it is true that each system could point to its own resources (or 'light-modules') directory, and that a developer could deploy different yaml configuration files to each of them - in practice this would be difficult to do and maintain. We require an easier and more transparent and maintainable way to achieve this. Bigger Picture A related need is to provide different configuration to differnet 'environments' like dev, integration, production. When considering a solution to the author/public issue - consider this too and find a way that would at least be compatible with the environments issue, and at best be a solution to it as well. Context During free trials development there was the need to apply different configures on publics and author in order to don't show a 404 page when accessing SPA demo. The issue has been solved with work arounds but we would like to raise the attention to provide the option. Discussion about: https://magnolia-cms.slack.com/archives/C010SQYMGGP/p1595230252240700 Description by Topher
Demo/Review of the approach implemented: https://magnolia-cms.zoom.us/rec/share/1NxyE7bSpz9IaInc0G-HZvQhOYPpT6a80CBI86IFz0-uE3kVdmN9wFuyV6jP3O7n |