I've used VLT for this as well. It's nice as you can target the path to update but it is clunky. From a speed perspective, you could also use an S3 bucket to transfer the content if you are using AWS so each script only cares about its local environment and you don't need to allow direct access between servers.
On Mon, Oct 23, 2017 at 11:58 AM, Robert Munteanu <romb...@apache.org> 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 >
