Getting started guide for development with Adobe Experience Manager and Docker.
Getting started guide for development with Adobe Experience Manager together with Docker. The configuration contains an AEM author, publisher and dispatcher environment, running in three separate containers. Docker images also have support for installing AEM packages during build.
This tutorial assumes running on a Mac. Installation on Windows might differ for certain steps. The following items are required:
AEM_6.2_Quickstart.jar
or AEM_6.3_Quickstart.jar
(other versions might work, but are not tested)license.properties
oak-run-*.jar
, where the *
contains the version number. Make sure the Oak version is compatible with the AEM version../author/packages/
and ./publisher/packages/
. Order of installation will be alphabetically, based on package file name.docker build -t aem-base -f base/Dockerfile . && docker-compose build
. This takes a couple of minutes (or more, depending on the number of packages), as the author and publisher are started during build to be able to install packages.docker-compose up
. This will also mount the ./logs
directory on your local system to the containers, so you have easy access to the logs of all containers.Active
or Fragment
the AEM environment has fully started.admin
and password admin
. Navigate to http://localhost to see the published site via the dispatcher. The publisher runs on http://localhost:4503.Starting and stopping containers preserves AEM content. Images need to be rebuild when changing packages in the packages
directories. After stopping a container, or after a system reboot, you can be quickly up-and-running again by starting the containers with docker-compose up
.
brew cask install java8
.brew install maven
.brew cask install caskroom/cask/intellij-idea-ce
.Edit Configurations
. Add a New Configuration
with the plus-icon on the top-left corner, select Maven
. Set the name as Deploy author
, set the working directory as aem-sample-we-retail
, command line clean install -e
and profiles autoInstallPackage
. Now save the configuration.Deploy author
configuration. You might get an error that the Java JDK can't be found: Project JDK is not specified
. When this occurs, click on Configure
next to the error and specify the location of your Java SDK (for instance, /Library/Java/JavaVirtualMachines/jdk1.8.0_162.jdk/
). Now try again to run the Deploy author
configuration and you should see a success message.we.retail.*
packages on top of the list.Inspiration and code examples are taken from the following projects: