Single Node Reference Implementation
This reference implementation demonstrates how the dotCMS provided containers can be configured to function together on a single host node. This configuration uses internal caching only (no external hazelcast node) and a single external ElasticSearch node.
For this configuration to work properly, you need to have a valid license pack mounted into the dotCMS image. You can do that by replacing this line:
with a line like:
where the path before the colon points to the license pack on the host filesystem.
You should have at least 5GB of RAM dedicated to Docker for all of the containers to run. If you are running this stack for a production system, normal capacity planning is needed to determine the amount of resources needed to effeciently handle system load.
- Ensure license pack is mounted properly into the dotCMS image as discussed above.
- In the same directory as the docker-compose.yml file, run:
- Wait for dotCMS to finish starting up. The inital startup takes an extra amount of time as it has to create the schema and data for the database. You know that it is finished starting and intializing when you see
Deployment of web application directory [/srv/dotserver/tomcat-8.5.32/webapps/ROOT] has finished in...
- Now you can access dotCMS via http://localhost/ (or by other relevant IP or DNS entry)
- In terminal window where docker-compose was run, hit
<Ctrl-C>This will causing the docker services to stop.
- To ensure the networks are stopped and all containers have been stopped cleanly, run
- These commands will stop all containers and docker networks that were started; however, the data has been persisted in named volumes.
- The command
docker volume lswill list all of the docker volumes. If you wish to remove volumes, you can use the
docker volume rm ...syntax.