I just joined this list, apologies if this is not in context. I assume you
mean purely the Jackrabbit repository. I'd be very interested in the best
approaches here as well.
I currently have 2 approaches:
1. Wrote a custom export/import tool which is particular to my data. It
actually wasn't too complicated - but very proprietary. The export results
(mixture of file data and property files) is then backed up and managed
accordingly for importing into any environment.
2. DB Dump/tar - depends on your repository configuration:
- With purely file based, you can just tar up the jackrabbit directory
and move it around.
- Otherwise, you'll have to also dump your cms db, tar up repository
directory and promote both around.
In both cases, there's the idea of official cms data managed outside of
dev/qa/staging/prod envs.
-Robert
On Mon, Aug 31, 2009 at 4:26 PM, Josh Kennedy <[email protected]> wrote:
> First off, thanks to Bertrand and Vidar for their quick responses.
>
> One thing I have been looking at with Sling, and was wondering what other
> people are doing is moving content from Development, into Staging and
> Production.
>
> I'm interested in what workflows people have found useful, and in what ways
> others are transporting content between different Sling instances for
> development and through production.
>
> Thanks again for the assistance.
>
