You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Would it be possible to provide a simple, localhost, author to author sync example? I.e. the most basic scenario, syncing between two development AEM instances on a localhost environment. I did get the old tool working, but I'm struggling to get this new version going (not sure if its pebcak or bug!) and a KISS example would be appreciated.
On the KISS topic, I think it would be helpful if all references in documentation and configuration files were either "sourceServer" or "destinationServer".
Since there are multiple configuration files, having names in docs and configuration items like serverUsername, localhost, author is a bit confusing - I would think the tool is agnostic to all this and should work with simple a "source" and a "destination".
I'd also welcome the evolution of this tool to a more KISS orientated approach; I'm sure there are design reasons and use cases for the current approach but the decade old command line paradigm of ./command -arguments /path /path with a line by line output to stdout is tried, tested and popular for a reason :)
Looking forward to seeing where this all goes; even in its current state its super cool. Thanks!
Completely agree with essentially everything you said, @timdonovanuk
The tool was built as "the simplest thing that could possibly work" within our infrastructure at Time Warner Cable, but it's clearly extremely specific to that setup. I'm currently trying to both improve the documentation as well as making the way that you interact with Grabbit (the CLI as well as its REST interfaces) more flexible.
That said, of course, doing so is a "on my own time" effort since it works well enough for work purposes. So any help (including even just small documentation changes) via pull-requests would be very appreciated.
Activity
jdigger commentedon Jul 11, 2016
The test resources area is probably your best quick bet: https://github.com/TWCable/grabbit-cli/tree/master/src/test/resources
jdigger commentedon Jul 12, 2016
Otherwise, the section of the Grabbit docs that you likely want to reference is https://github.com/TWCable/grabbit#configuration
timdonovanuk commentedon Jul 20, 2016
Would it be possible to provide a simple, localhost, author to author sync example? I.e. the most basic scenario, syncing between two development AEM instances on a localhost environment. I did get the old tool working, but I'm struggling to get this new version going (not sure if its pebcak or bug!) and a KISS example would be appreciated.
On the KISS topic, I think it would be helpful if all references in documentation and configuration files were either "sourceServer" or "destinationServer".
Since there are multiple configuration files, having names in docs and configuration items like serverUsername, localhost, author is a bit confusing - I would think the tool is agnostic to all this and should work with simple a "source" and a "destination".
I'd also welcome the evolution of this tool to a more KISS orientated approach; I'm sure there are design reasons and use cases for the current approach but the decade old command line paradigm of ./command -arguments/path /path with a line by line output to stdout is tried, tested and popular for a reason :)
Looking forward to seeing where this all goes; even in its current state its super cool. Thanks!
jdigger commentedon Jul 20, 2016
Completely agree with essentially everything you said, @timdonovanuk
The tool was built as "the simplest thing that could possibly work" within our infrastructure at Time Warner Cable, but it's clearly extremely specific to that setup. I'm currently trying to both improve the documentation as well as making the way that you interact with Grabbit (the CLI as well as its REST interfaces) more flexible.
That said, of course, doing so is a "on my own time" effort since it works well enough for work purposes. So any help (including even just small documentation changes) via pull-requests would be very appreciated.