Docker AEM
This project holds all our 6.2 AEM docker images we have built so far. At this time we have only completed and tested the standard tar MK based images. We will be working to include more as time goes on.
The easiest way to get start would be to clone this repo then from the cloned root directory run the following command
./makeLocalImages.sh
note: you may need to allow execution on this script (chmod +x ./makeLocalImages.sh)
This command will build the base, publisher and author image locally and will prompt you to supply your AEM jar and license file. Then it will build out the dispatcher image for you.
After that is done running the next step would be to change to the composedev-tar directory and run the start-containers.sh script to bring up all three containers for you.
You will need to build the following images locally first before running the start-containers.sh script from the projects directory. You may need to add execute permissions to the script before running it (chmod +x ./start-containers.sh)
./start-containers.sh
The start-containers script will execute docker-compose up -d to bring the containers up in the background and leave them running. Once started it will execute docker-machine ls to get the IP of the virtualbox where the containers are running and print out friendly URLs for the Author, Publish and Dispatcher instances.
Install additional packages
The system also allows for the ability to install additional packages such as hotfixes, featurepacks etc. Currently this is done per AEM image (author and publish). Each of the author-tar and publish-tar directories contain a packagelist.txt file and packages directory under the resources directory. The packagelist.txt file should contain a list of packages to be installed with each line of the file representing one package. This way we can guarantee the order of installation of the packages which in some cases in AEM is important.
The /resources/packages directory is where the actual packages are expected to be placed and this is where the installation script will look for them. Currently only packages (.zip files) are supported.
How are the AEM instances configured? Each of the AEM images (author, publish) are configured via quickstart properties. The quickstart file that is responsible for the configuration can be found under each images resources subdirectory.
This has only been tested on a Mac system at this point.
Another note: If your running these images on your MAC you will need to adjust your Virtual Box memory settings. The default boot2docker vm image only has 2 gigs alocated for memory and these images need 2 gigs each. I think I need to come up with a better solution so its easier to use on smaller dev machines. To alter your Virtal Box memory settings find the Virtual Box app and run it and then select the boot2docker vm and adjust its settings and add memory. In some of the beta versions of Kitematic it will use a VM named dev and not the boot2docker vm image.