[MGNLSITE-92] YAML site definitions & default targets Created: 26/Nov/18  Updated: 07/Jun/22

Status: Accepted
Project: Magnolia Site Module
Component/s: api
Affects Version/s: None
Fix Version/s: None

Type: Epic Priority: Neutral
Reporter: Mikaël Geljić Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: light-modules, multisite, research, site
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MGNLSITE-102 DOC: Yaml-based site definition howto... Closed
Template:
Epic Name: YAML site definitions
Acceptance criteria:
Empty
Date of First Response:

 Description   

Building upon research for Default Target URI mapping, we want to drive this initiative further and open Site definitions to light development.

With YAML sites in mind, it is foreseen that we will configure all domains (for all instances in a project) in the same single site definition
—effectively having extra domains configured, even if a given instance is not bound to that domain.

One side-goal to this is to remove the need for per-instance JCR configuration regarding site/multisite setup.



 Comments   
Comment by Roman Kovařík [ 25/Mar/19 ]

Worth evaluating if this was not superseeded by MAGNOLIA-6521.

Comment by Christopher Zimmermann [ 13/Apr/21 ]

https://jira.magnolia-cms.com/browse/MAGNOLIA-6521 Does solve some of the problems, but no it does not supercede this ticket.

Generated at Mon Feb 12 07:12:39 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.