Could someone point us to a url explaining where the node and security settings are stored in the file system? I'd like to configure the roles, dialogs, paragraphs, and templates in our Dev environment, then commit and release them via CVS.
-----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] Sent: 14 July 2006 15:30 To: [email protected] Subject: Re: [magnolia-user] templates outside of webapp? Chris, We store and release the docroot and templates folders via CVS. A release script deletes these folders before copying in the new ones. For the first production release, we'll active the nodes from our QA environment to the Production environment, but I'm thinking that when we release templates in the future (via CVS) that we'll document adding and activating the node settings for the new templates in the public authoring instance. I'm interested to hear how others are handling new template nodes as well. After the initial release, I don't want to be activating from QA to Production, as we want them to be independent environments. Ben -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] Sent: 14 July 2006 12:21 To: [email protected] Subject: [magnolia-user] templates outside of webapp? Hi All, In working through the tutorials and documentation about how to use magnolia, we're directed to edit/place files in the deployed app. To facilitate this, I have the source checked out and built in eclipse and add my new templates to that projects. While this seems okay for a learning experience, it doesn't seem practical in practice. How are people handling the development / deployment cycle for new templates, dialog, and paragraphs? Are people just working on their live Authoring Instance directly? Or do you have some sort of development / staging model that allows for reviewing/checking work before doing a deployment for the people doing your content management work? What about updates to existing templates, dialogs, and paragraphs? Or related localization info? Cheers, Chris ---------------------------------------------------------------- for list details see http://www.magnolia.info/en/magnolia/developer.html ---------------------------------------------------------------- ---------------------------------------------------------------- for list details see http://www.magnolia.info/en/magnolia/developer.html ---------------------------------------------------------------- ---------------------------------------------------------------- for list details see http://www.magnolia.info/en/magnolia/developer.html ----------------------------------------------------------------
