Forum OpenACS Development: Re: Major enhancement to the installer; minor enhancement to the default index page

Now if we could find a way to make an installed OACS instance create one of those "install.xml" babies as a snapshot of its current state, I can imagine even better things happening...

This mechanism might come in handy when running multiple OACS instances with the same setup and different database table spaces (say, development and production servers). Maybe an "update.xml" file could encapsulate the admin actions like package installation, parameter setting and all the other database-dependent things that cannot be handled through CVS.