[
http://jira.magnolia.info/browse/MAGNOLIA-2132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16164#action_16164
]
Simon Goodchild commented on MAGNOLIA-2132:
-------------------------------------------
I know quite a few people (myself included) have developed slightly kludgey
solutions to this problem (see user list and wiki), so an easier and more
standardized solution within the magnolia core would be very useful. The memory
use improvements in recent releases have made it more viable to run multiple
instances, and there will always be cases where it is better to separate things
completely like this, but there are also many instances where a shared solution
would work much better. A classic example of this is multiple small microsites
- it is impractical to run say 50 instances of magnolia when each one only
contains 5-10 pages, but there are also administration benefits to using a
shared system:
- You can use the same set of standard dialogs across each site, with easier
deployment of changes to these to one system instead of 50
- Setting up a new site is just a case of copying or importing an existing
site, so no need to configure app server, RDBMS, boostrap, etc. each time
- There is just one set of administrator credentials, so easier to change these
in one place if you need to
- Easier to monitor the system, as if the single shared instance is up then all
the sites should be
That's just off the top of my head, but there are probably plenty more!
Regarding the high-level approach to how we could go about doing this, the
approach all out kludgey solutions have taken is to have a separate root node
for each site and apply permissions and Web server mappings to allow access.
That would seem the obvious choice for a core product solution, and make
migration from existing solutions easier for everyone. When I was architecting
the approach to my own kludge I also considered the alternative of a separate
workspace for each site - that would provide better separation but not sure if
that is makes things significantly easier or harder for implementing this new
function?
We would use this function extensively, so I'm happy to devote some development
time to it once we have an approach agreed. I haven't done a huge amount of
development on the core magnolia code, so would need some guidance, but should
be able to pick things up quite quickly.
Simon
> One Magnolia to rule them all
> -----------------------------
>
> Key: MAGNOLIA-2132
> URL: http://jira.magnolia.info/browse/MAGNOLIA-2132
> Project: Magnolia
> Issue Type: Improvement
> Components: core
> Reporter: Fabrizio Giustina
> Assignee: Fabrizio Giustina
>
> In some situations it would be great to have the ability to use a single
> magnolia authoring instance + a single public instance for managing more
> websites.
> We encontered similar requirements several times in the past and may want to
> work at adding a better support for this in Magnolia. I'll use this as a
> master issue in order to group any related issue or needed enhancement for
> this.
> Open for discussions :)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia.info/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/
----------------------------------------------------------------
