aft a few proposals, maybe we can use those to shoot
at them and come to the right solution.
With kind regards,
Henry Kuijpers
From: Carsten Ziegeler
Date: Tuesday, 8 June 2021 at 09:05
To: dev@sling.apache.org
Subject: Re: Ability of scoping sling:vanityPath per content path
Hi,
yes, I
few proposals, maybe we can use those to shoot
at them and come to the right solution.
With kind regards,
Henry Kuijpers
From: Carsten Ziegeler
Date: Tuesday, 8 June 2021 at 09:05
To: dev@sling.apache.org
Subject: Re: Ability of scoping sling:vanityPath per content path
Hi,
yes, I think
Hi,
yes, I think supporting such scoping makes sense.
In general, we must preserve existing functionality - how about opting
in to the scoping by using a special prefix as part of the value for the
vanityPath like sling:vanityPath=map:/openinghours?
(map: might not be the best prefix, but ju
Henry Kuijpers created SLING-10466:
--
Summary: Ability of scoping sling:vanityPath per content path
Key: SLING-10466
URL: https://issues.apache.org/jira/browse/SLING-10466
Project: Sling
The sling mappings provide the possibility of creating a multi-tenant setup.
Multiple websites can be hosted, by providing Sling mappings that point to
their specific content paths. These mappings consist of domains. I.e.:
* https://my-website-a.com/ -> /content/my-website-a
* https://my
