Short answer is there isn't a package manager in sling or jackrabbit at the moment. Crx has one but that's commercial. You could probably write an exporter/importer which exports a given path and its children using the document formats as a zip file.
Also, please note that even though you have versioning in the osgi bundle, the content you package up in there in SLING-INF will be overwritten in JCR. So a reverting from 0.2 to 0.1 means you need to remove 0.2 bundle and reinstall 0.1 bundle (I think). Sarwar On Wednesday, March 20, 2013, Fabian Christ wrote: > 2013/3/6 Bertrand Delacretaz <[email protected] <javascript:;>>: > > [...] and if you see gaps feel free to > > discuss! > > I am catching up on my evaluation of Sling (and I am taking notes). > > I see one gap where I am not sure how to proceed. Let's say I have > created my server side scripts and templates under '/apps'. Now the > Sling way IIUC is to model the RESTful interface of my web app using > the JCR, i.e. create nodes in '/content' with proper resourceType > annotation etc. > > The stuff in /apps can be packaged as an OSGi bundle and by this > versioned like any other software component. It can also be easily > deployed. > > The stuff in the JCR (which is the RESTful interface) is different. > How should I handle this on deployment to another machine? How is > versioning supported here? Jackrabbit itself provides some way of > backup - is this the way to go? I have a feeling that this is the kind > of tooling that people may have @work but that creates a gap in the > usability of Sling for others. > > -- > Fabian > http://twitter.com/fctwitt >
