| 1 | aemsync
|
| 2 | =======
|
| 3 |
|
| 4 | AEM (Adobe CQ) Synchronization Tool.
|
| 5 |
|
| 6 |
|
| 7 | ### Installation
|
| 8 |
|
| 9 | With [npm](http://npmjs.org) do:
|
| 10 |
|
| 11 | ```
|
| 12 | npm install aemsync -g
|
| 13 | ```
|
| 14 |
|
| 15 | ### Usage
|
| 16 |
|
| 17 | ```
|
| 18 | aemsync -t targets [-i interval] -w path_to_watch
|
| 19 |
|
| 20 | -t: Comma separated list of hosts.
|
| 21 | -i: Update interval; default 300 ms.
|
| 22 | -d: Enable debug mode.
|
| 23 | ```
|
| 24 |
|
| 25 | ### Example
|
| 26 |
|
| 27 | ```
|
| 28 | aemsync -t http://admin:admin@localhost:4502 -w ~/workspace/my_project
|
| 29 | ```
|
| 30 |
|
| 31 | The path has to contain jcr_root folder. File system changes inside the folder will be picked up and pushed to AEM instance as a package. There is no vault dependency.
|
| 32 |
|
| 33 | Sync interval is the time the syncer waits for changes. In case of multiple changes occuring at the same time (e.g. switchig between code branches), we want to avoid creating a separate package for each change, but rather send all in one go. Lowering the value removes the delay from single changes but increases the delay for multiple changes. It is all about finding the right ballance. |
| \ | No newline at end of file |