Hi Gregory, Yep, we always build our own webapp. :-)
But the thing is that ideally we would like to start from scratch for every new deployment on our test environment. And this means: clean/remove the JCR repo's and do the entire Magnolia installation (including sample content) everytime. Right now we are thinking of writing a custom servlet (filter) in our webapp that cleans up the JCR repo's (database + filesystem) depending on an env variable being set (scary..) before Magnolia starts up. Alternatively we could just use the default Derby filesystem database and store the entire JCR repo's inside the web app folder (which is something that we otherwise never do) and remove the web app folder for every deploy with the JCR repo's inside it.. cheers, Edgar -- Context is everything: http://forum.magnolia-cms.com/forum/thread.html?threadId=18e003d6-1ed0-49cf-8f3b-4ebc4502e5ae ---------------------------------------------------------------- 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: <[email protected]> ----------------------------------------------------------------
