You might be able to do what you describe about, but consider this: - the transport layer for pushing content from Magnolia to Apache is something you would have to write yourself (And it might not be simple since Magnolia doesn't generate html until it is requested and even then it might be specific to given user (locale, location, time, ...) - all your content will be static only, so you are giving up on advantage of being able serve different content to different visitors or change it dynamically that you have in Magnolia out of the box - on every activation you might have to flush all and start again or determine dependencies (e.g. navigation titles are generated from page titles so publishing single page somewhere high up in the hierarchy that is used in navigation and changing as little as just the title of that page will force you to dump everything and start pushing to apache again) - and there's more drawbacks to your proposal
So why don't you just use multiple public instances of Magnolia? -- Context is everything: http://forum.magnolia-cms.com/forum/thread.html?threadId=30708b89-29fa-4bde-90bf-b19a8b064c31 ---------------------------------------------------------------- For list details, see http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: <user-list-unsubscr...@magnolia-cms.com> ----------------------------------------------------------------
