Thanks for replying, Sameer. I think I'm following you, but I want to make sure I understand what you're referring to as "bootstrap." Is this your suggested process?
1. Change all my configs to my liking in my dev environment 2. Export the configs as xml 3. Check the xml config file into SVN/CVS 4. Import the xml config into a testing/production environment to release them Also, what do you mean by "create a development template which reads config bootstrap files"? Are you suggesting creating a page that you'd visit to take the manual steps out of the import in the release environment? Ben -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] Sent: 24 August 2006 09:47 To: [email protected] Subject: Re: [magnolia-user] Your strategy for releasing Configs Hi Ben, why don't you keep the exported xml files on your CVS like we do for magnolia under bootstrap. we usually bootstrap everytime we update code from SVN but you could also create a development template which reads config bootstrap files and import it using magnolia api. Regards, Sameer Charles Magnolia International Ltd. ------------------------------------------------------------------------ --------- [EMAIL PROTECTED] http://www.magnolia.info Magnolia(r) - Simple Enterprise Content Management ------------------------------------------------------------------------ --------- On Aug 24, 2006, at 10:31 AM, Ben Brock wrote: > If someone out there is releasing config nodes outside Magnolia, > please share your process. > > -----Original Message----- > From: [email protected] [mailto:[EMAIL PROTECTED] > Sent: 23 August 2006 16:53 > To: [email protected] > Subject: [magnolia-user] Your strategy for releasing Configs > > How do you guys release your Config nodes? > > Releasing via activation in Magnolia is not a scalable, protected > approach. Changing their values and putting repositories/config folder > in CVS doesn't seem like a viable solution either. Ideally you would > check out the configs to a dev environment, change them, check them > in, then release them as you would the templates. > > Any suggestions?? > > Ben Brock > > ---------------------------------------------------------------- > 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 ---------------------------------------------------------------- ---------------------------------------------------------------- for list details see http://www.magnolia.info/en/magnolia/developer.html ----------------------------------------------------------------
