This is exaclty what I want to do, except finding out the specifics of how to do it is really hard for me :/
Is any one able to point me to either a wiki entry or a mailing list message (i've searched and come across all the questions related, but the answers are thin on the ground) I'm sure if I spent a few weeks/months I could work how Magnolia works/functions and then from that fit what I want to do into the magnolia platform. But like most people I don't have this sort of time... Magnolia is a pretty sweet platform from what I've been able to learn in the last two weeks, but figuring it all out to do what I want to do is mystifying ;) I have so many questions and the answers are not exactly apparent. If I had a spare 15grand (AU$) I'd be on the blower to the developers :) Thanks for all pointers. Nick Magnolia - User mailing list wrote: > > Hi Everyone, > finally our customer is ready and we want to start implementing their > site on Magnolia. Now our customer has 11 individual sites, all > belonging to the same company. After our brief experience of doing one > small project in Magnolia we would try to do the following: > - Install the magnoliaAuthor/magnoliaPublic duo > - create a root folder for each website of our customer > - create the en/de/fr folders in each website folder > - create the websites in these folders accordingly ( so it would be > example1/en/* ) > - create virutal hosts for these subfolders, so that www.example1.com > shows that part of the tree > Now so far we think this would work best, editors can be given access > only to specific websites and subtrees, we only need one instance of > Magnolia (instead of 11). The only slight disadcantage would be, that we > cannot (or can we?) assign templates to only a part of the tree, so an > editor could accidentally assign the template of a different website to > the page under his tree. > We have managed to set up virtual hosts in Tomcat to map the domain to > the magnolia instance, but have no experience setting up multiple > virtual hosts to point into seperate subfolders of the SAME Magnolia. > Has anyone tried something like this? Would anyone caution us against > going this way? > Many thanks, > Martin > -- View this message in context: http://www.nabble.com/Any-reason-not-to-do-multiple-sites-in-one-magnolia--tf678870.html#a10070696 Sent from the Magnolia - User mailing list archive at Nabble.com. ---------------------------------------------------------------- for list details see http://www.magnolia.info/en/developer.html ----------------------------------------------------------------
