On 22/10/2017 19:39, Roy Teeuwen wrote:
>
> * One could create a JCR content package of production, and copy it
> over to the different environments daily. The downside of this is
> that when the package becomes big, it gets problematic (for
> example when a lot of images/videos
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
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
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
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
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
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
