Hello everyone,
I'm working on an AEM as a Cloud Service project. I want to test dispatcher rules but I don't want to deploy every time I make a change.
Is Docker necessary to have a 'local dispatcher'?
If I have a multi-module Maven project, is it enough to copy the conf.d folders from the module to my dispatcher folder?
I'm quite lost, so if you could shed some light, that would be great.
Best regards!
Solved! Go to Solution.
Topics help categorize Community content and increase your ability to discover relevant content.
Views
Replies
Total Likes
The AEM SDK's dispatcher with docker provides a quick way to set it up. You can also make changes in the Docker Image directly, verify the changes and copy your files back to maven project.
Otherwise you can set up a dispatcher locally and sync the files. Structure and rules. It should still work.
Setting up a dispatcher via Apache webserver https://aemtutorials.com/dispatcher-setup-in-aem-6-4/
The AEM SDK's dispatcher with docker provides a quick way to set it up. You can also make changes in the Docker Image directly, verify the changes and copy your files back to maven project.
Otherwise you can set up a dispatcher locally and sync the files. Structure and rules. It should still work.
Setting up a dispatcher via Apache webserver https://aemtutorials.com/dispatcher-setup-in-aem-6-4/
Hi @Jniza, as explained by @aanchal-sikka, you can take advantage of the dispatcher tools which come as part of the AEM SDK. Here, you will find a docker dispatcher image for your convenience, so you don't have to set up a dispatcher locally; instead, you can simply mount the dispatcher image in your docker engine.
Additionally, there is a script that allows you to perform a "hot reload" for dispatcher configs and validation, which I believe is what you are looking for.
You can find instructions on how to use it here. it: https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/implementing/conten...
Views
Likes
Replies
Views
Likes
Replies