Skip to content

Watch file changes and auto deploy them to AEM

Jump to bottom
Kevin Weber edited this page Jan 23, 2018 · 6 revisions

By default, you have to run a Maven build in order to deploy code changes to a (local) AEM instance. Because Maven builds can take multiple seconds or minutes, it's recommended not having to run them for certain changes, especially in XML, HTML, JavaScript and CSS files.

There are multiple ways to achieve this, for example:

  • Use AEM Front which combines aemsync & BrowserSync modules. Note that this project uses AEM Front. It is automatically run with the npm start script.
  • Develop code in Brackets editor with Adobe's AEM Brackets Extension
  • Use the original aemsync module

AEM Front

Many developers prefer AEM Front because it isn't tied to a specific editor (such as Brackets) and it automatically reloads sites in Google Chrome when combined with the AEM Front Chrome Extension.

AEM Front is usually installed as a global NPM module and run from the root folder of an AEM project on the command line. In addition, you should run a Webpack watch script that comes with the AEM Webpack Example project so it compiles your front-end code.

Note that AEM Front can also be integrated directly into the Webpack setup. More details here.

One of the best and most trusted AEM consultancies is hiring!

Clone this wiki locally