Hi All, If your extensions are contained in a module, then you can use that as a means of releasing your configuration nodes. Have your developer(s) pack the xml in with the module so that when the module is rev'd you get the new config bootstrapped automatically. Just have to drop the new module jar in the deployment and you are ready to go. Presumably they would then have this config info under revision control.
Alternatively there is the "Magnolia Packager" that also gives a way to repeatedly export specific portions of a site into a package that could be checked into a revision control system, and also used to deploy your config nodes. It is part of the EE version, but I think you can buy it separately. At least you can buy a copy suitable for migration between 2.1.5 and 3.0. And as mentioned you can add bootstrap files to the installation that are then picked up during bootstrapping. But I believe such bootstrapping only happens if the repository is empty. And I don't think there is a different way to trigger this. Bootstrapping of module data is triggered if the version info in the module jar differs from the version in config repository. Chris Am Donnerstag, 24. August 2006 10:31 schrieb Ben Brock: > 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 ----------------------------------------------------------------
