Hi Roy, This is a use case that we have as well.
We need to be able to sync content between different instances periodically or on request. We are still in the planning phase and will start to implement Sling once we have enough resources. Please share your experience so others can benefit (including us). In our use case we have an Item Bank with lots of items and other content. Most of the time we need to update translations. In some cases (once every few months) we need to add/update the content/content structure. Translations can be handled in lots of ways, we might not even use the vlt solution Robert proposed. For new content I think that is something that will help us. Regards, On 23.10.2017 18:58, Robert Munteanu wrote: > Hi Roy, > > On Sun, 2017-10-22 at 19:39 +0200, Roy Teeuwen wrote: >> Hey guys, >> >> I didn't know for sure where to put this question so thats why I am >> asking it in both Jackrabbit as in Sling, because both might have >> their own solution / proposal, and I have seen solutions that are >> pure Jackrabbit but some that also require Sling. >> >> I was wondering about what some of you might achieve something like a >> daily content sync between different environments (Production to >> Acceptance/Development for example). > Never tried this, but maybe you can use vlt ci/co? Initially you run > vlt co against the 'source' instance and then vlt ci against the > 'target' instance. First time you will sync everything, but then > operations will be incremental. > > You do have to find a clean way of switching the vlt url between > invocations though. > > Robert
signature.asc
Description: OpenPGP digital signature
