The way you deploy and run the Alfresco Community Edition solution has changed significantly in version 6.0. Traditionally you would download an installer that would install Java, Tomcat, Database, WARs, tools, etc, and things would be configured to work together. Then you would use a script to kick things off. That’s no longer the case and there are no installers available. We will be working with Docker containers instead.
It’s now possible to kick off an ACS 6.0 solution from a number of Docker images. These images are available in the https://hub.docker.com repository. However, kicking off individual Docker containers based on these images, and configuring them to work together, might not be the most productive way to get up and running with ACS. To make things easier, and achieve a one-click to deploy and run solution, a Docker compose file is available to quickly deploy and run the ACS solution when you need to test something or work on a proof-of-concept (PoC).
There are also Helm Charts available to deploy the ACS solution in production as a Kubernetes cluster in for example AWS.
When the ACS solution is deployed with Docker it looks something like this:
- alfresco/alfresco-share - the Alfresco Share web interface (i.e. share.war) running on Apache Tomcat
- alfresco/alfresco-search-services - the Solr 6 based search service running on Jetty
- alfresco/alfresco-content-repository-community - the Alfresco Repository app (i.e. alfresco.war) running on Apache Tomcat
To build the alfresco/alfresco-content-repository-community image Alfresco uses the https://github.com/Alfresco/acs-community-packaging project. This project also includes a Docker Compose script that can be used to launch a demo, test, or PoC ACS 6.0 system. You can customize this script if you like in order to run with different versions than those set by default, which are usually the latest versions.
ACS 6.0 cluster deployments are managed via Kubernetes container orchestrator. The deployment architecture is defined with the Helm tool.