Package Exports
- aemsync
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (aemsync) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
aemsync
AEM (Adobe CQ) Synchronization Tool.
Installation
With npm do:
npm install aemsync -gUsage
aemsync -t targets [-i interval] -w path_to_watch
-t: Comma separated list of hosts.
-i: Update interval; default 300 ms.
-d: Enable debug mode.Example
aemsync -t http://admin:admin@localhost:4502 -w ~/workspace/my_projectThe 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.
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.