Hi Thomas,
we are am working on a tool called "Packaging for Magnolia" which will
help you
and the community. As we can say today there will be a free version for the
community to share templates, styles, ... and a commercial version to support
deployment, maintenance, update. Stay tuned.
With Packaging For Magnolia you define a package based on rules (include /
exclude ACLs) for all repositories and the files of the webapp as well.
With the free version you will have the following possiblilities:
- define a package
- create and download a package, so you can share it
- upload a package
- install a package (this will generate a undo package)
- uninstall a package (by installing the undo package)
For example use Packaging For Magnolia to exchange templating. The templating
package could consist of
- template jsps
- paragraph jsps
- docroot fileds like css, js and graphics
- template config from config repository
- paragraph config from config repository
The commercial version will have some extra features like:
- versioning of packages (and undo packages)
- activation and deactivation of packages
- some kind of backup using http-Protokoll
-- define a package
-- use a defined URL to download the backup package
-- this is a snapshot of your system according the package rules
Ralf
Anyone tackled this issue?
Ie is there a possibility to trigger the export.xml NOT through the
web interface but via ant or equivalent?
that would be nice.
On Jan 19, 2006, at 21:42, (Thomas Ferris Nicolaisen) wrote:
(note that I still export/import JCR-content manually, this
includes dialog and paragraph configuration).
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
