Developing AEM Dispatcher configuration can be challenging. The same attribution goes to httpd configuration, especially for developers without a broad experience with it. This article will show how to release this pain with Gradle AEM Plugins using its live reload feature.
AEM instance setup using Gradle post presented how to set up AEM instances using Gradle AEM Plugins. In this blog post, you will see how to extend this previous example with AEM Dispatcher to model a production environment locally. What is more, we will cover "live reload" mode (the concept known from many JS frameworks), where each code change is immediately reflected in the application itself.
How to use this post?
There are two ways you can benefit from this article. You can read it entirely to have a good understanding of how the Environment plugin manages Dispatcher. You will know where to change the defaults and how to set up your projects.
On the other hand, if you only want to explore the live reload feature, please cover Prerequisites section, then download our example GAP project running AEM with Dispatcher, update the gradle.properties file and navigate directly to Setting up the environment to continue reading.
Quick reminder: Configure AEM
Let's start from the place, where we had AEM instances configured and running - both author and publish on our local machine. Let's quickly review how our configuration looks like:
│ └── wrapper
│ ├── gradle-wrapper.jar
│ └── gradle-wrapper.properties