|
All content with label multi-site.
Related Labels:
v2_1, deployment, config, administration, v3_0, v3_5, apache, acl
Setup editor role for a site
(Community Wiki)
Setup Editor role for a site If you want to run several sites on your magnolia instance you want to give them rights so that they can only see their own content: Suppose you have a strucure like this /site1 /site2 ...
Other labels:
acl, administration, config
|
Restrict template selection
(Community Wiki)
straightforward to restrict access to templates using ACLs For instance, group your templates per site and deny access to the folders that a role should not have access to. E.g. try the following: deny access to CONFIG: /modules/templating/Templates/samples for role ...
Other labels:
config, v2_1
|
Running several sites with one Magnolia instance
(Community Wiki)
run several sites with one Magnolia instance (author and public) you can use Apache with modjk. Here is what you have to do: 1. Give every site a separate content tree. I.e., create a toplevel item in the "Websites ...
Other labels:
deployment
|
Rewrite URLs with Apache
(Community Wiki)
Requirement Magnolia is not designed to run multiple websites in a single instance, so workarounds are necessary to achieve this. The obvious solution is to have multiple instances. To make nice URLs as well (i.e. without {{MagnoliaPublic}}) requires a solution using Tomcat Virtual hosts ...
Other labels:
v2_1, v3_0, v3_5, apache, deployment
|
|
|
