[MAGNOLIA-1828] install: introduce properties to determine if a installation becomes a public instance Created: 08/Nov/07 Updated: 23/Jan/13 Resolved: 08/Nov/07 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 3.5 RC1 |
| Type: | Improvement | Priority: | Blocker |
| Reporter: | Philipp Bärfuss | Assignee: | Philipp Bärfuss |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| 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 |
|
For example the samples module sets a new default uri but only if this is a public instance. Since the bootstrap files of the webapp are bootstrapped at last the /server/admin property will still be set to true at the moment sample install tasks are executed. To steer that I introduce a optional property magnolia.bootstrap.authorInstance which is used by the core module to set /server/admin accordingly. In addition I also introduce magnolia.bootstrap.samples which can be used to determine if sample content (in modules like forum) should get installed In future versions the installation UI will ask for this kind of information. |