You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Markus Blaurock (JIRA)" <ji...@apache.org> on 2010/04/29 17:10:54 UTC
[jira] Created: (SLING-1513) allow host-specific rendering for
virutal hosts. "Multitenancy Support"
allow host-specific rendering for virutal hosts. "Multitenancy Support"
-----------------------------------------------------------------------
Key: SLING-1513
URL: https://issues.apache.org/jira/browse/SLING-1513
Project: Sling
Issue Type: New Feature
Reporter: Markus Blaurock
Currently we have the need to run multiple websites on the same
sling-instance. That is, serving the same or similar content in
different ways (layouts), defined by the hostname.
Reason behind this is we would like to have a single pool of sling-app-servers and
each one should be possible to serve all websites. Otherwise we would
need to have one pool for each (small) site, which is not feasible.
e.g. Content "a/b/c" should be accessible with
http://www.one/a/b/c.html
and
http://www.two/a/b/c.html
and looking differently.
https://cwiki.apache.org/SLING/multitenancy-support.html would solve the problem easily.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-1513) allow host-specific rendering for
virtual hosts. "Multitenancy Support"
Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-1513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler updated SLING-1513:
------------------------------------
Component/s: API
> allow host-specific rendering for virtual hosts. "Multitenancy Support"
> -----------------------------------------------------------------------
>
> Key: SLING-1513
> URL: https://issues.apache.org/jira/browse/SLING-1513
> Project: Sling
> Issue Type: New Feature
> Components: API
> Reporter: Markus Blaurock
>
> Currently we have the need to run multiple websites on the same
> sling-instance. That is, serving the same or similar content in
> different ways (layouts), defined by the hostname.
> Reason behind this is we would like to have a single pool of sling-app-servers and
> each one should be possible to serve all websites. Otherwise we would
> need to have one pool for each (small) site, which is not feasible.
> e.g. Content "a/b/c" should be accessible with
> http://www.one/a/b/c.html
> and
> http://www.two/a/b/c.html
> and looking differently.
> https://cwiki.apache.org/SLING/multitenancy-support.html would solve the problem easily.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-1513) allow host-specific rendering for
virtual hosts. "Multitenancy Support"
Posted by "Markus Blaurock (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-1513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Markus Blaurock updated SLING-1513:
-----------------------------------
Summary: allow host-specific rendering for virtual hosts. "Multitenancy Support" (was: allow host-specific rendering for virutal hosts. "Multitenancy Support")
> allow host-specific rendering for virtual hosts. "Multitenancy Support"
> -----------------------------------------------------------------------
>
> Key: SLING-1513
> URL: https://issues.apache.org/jira/browse/SLING-1513
> Project: Sling
> Issue Type: New Feature
> Reporter: Markus Blaurock
>
> Currently we have the need to run multiple websites on the same
> sling-instance. That is, serving the same or similar content in
> different ways (layouts), defined by the hostname.
> Reason behind this is we would like to have a single pool of sling-app-servers and
> each one should be possible to serve all websites. Otherwise we would
> need to have one pool for each (small) site, which is not feasible.
> e.g. Content "a/b/c" should be accessible with
> http://www.one/a/b/c.html
> and
> http://www.two/a/b/c.html
> and looking differently.
> https://cwiki.apache.org/SLING/multitenancy-support.html would solve the problem easily.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.