Hi,
I need to test some architectural solutions in order to choose the most
valueble choice for my customer.
In public context I need 4 different Magnolia instances in order to
start/stop/deploy a single instance indipendently of each others.
In author context I'd like to configure only one Magnolia instance. This
instance would be configured setting a root object for each repository
up to 4 distinct root object (each for every public instance).
Example:
/Public context/
Define 4 different public Magnolia instances: mgnlPbl1, mgnlPbl2,
mgnlPbl3 and mgnlPbl4
/Author context/
Define 4 root pages (homeMgnlPbl1.html, homeMgnlPbl2.html,
homeMgnlPbl3.html and homeMgnlPbl4.html) on website repository
Define 4 root folders (rootFolderMgnlPbl1, rootFolderMgnlPbl2,
rootFolderMgnlPbl3 and rootFolderMgnlPbl4) on dms repository
and so on for others repositories
Define 4 distinct subscribers (each for every site) giving them correct
urls and ACLs
MgnlPblSbsr1 on http://localhost:8080/mgnlPbl1
MgnlPblSbsr2 on http://localhost:8080/mgnlPbl2
MgnlPblSbsr3 on http://localhost:8080/mgnlPbl3
MgnlPblSbsr4 on http://localhost:8080/mgnlPbl4
Is it a good solution? Do I need to follow some particular ACL rules?
Any limitations to respect? Any tips related?
Best regards,
--
Giovanni Regola
Sol-Tec Soluzioni Tecnologiche Srl
Interno: +39 02 66 732 262
Cellulare: +39 340 0876513
http://www.sol-tec.it
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
