On a similar vein, another fun one we did a while back was to vlt co into a git repo and then blanket add and commit any changes on the hour. That way we had a snapshot of exactly what was going on in the repository and the ability to snapshot back any portion of the tree at any time (at a reasonable granularity level). Very useful in the throes of authoring where we were training up authors and trying to get a bunch of site content added at the same time.
On Mon, Oct 23, 2017 at 3:06 PM, Roy Teeuwen <r...@teeuwen.be> wrote: > Hey Ioan, > > In my initial post I already gave you all the experience I have so for, I > have tested out 4 different tools (Content Packages, VLT RCP, Grabbit and > oak-migration tool) and given my benefits and drawbacks. > > I will give VLT a try again, but I think seeing as the problem I found > when first using it through VLT RCP[1], so not the vlt co that Robert and > Daniel suggested, I am not sure if that one will work out. > If VLT fails and no other solutions come up, I might probably go for the > creating a daily content package based on a query which looks for new > content created that day. > > Greets, > Roy > > [1] http://jackrabbit.510166.n4.nabble.com/Filevault- > OakConstraint0021-Exception-td4666959.html > > > On 23 Oct 2017, at 18:53, Ioan Eugen Stan <ieu...@netdava.com> wrote: > > 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 > > > > >
