Alfresco Content Services Deployment
Please use this guide to make a contribution to the project and information to report any issues.
This project contains the code for starting the entire Alfresco Content Services (Enterprise) product with Docker or Kubernetes.
The master branch of this repository will endeavour to support the following deployments:
- Docker Compose (latest): For development and trials
- MiniKube (latest): For development and POCs
- Helm - AWS Cloud with Kubernetes using Kops (latest): As a reference or basis of production deployments
For the Community edition, go to the acs-community-deployment. The only differences between these projects are:
- In the Enterprise chart, the images for the transformers are used, instead of the included binaries.
- In the Enterprise chart, a cluster of two
alfresco-content-repositorynodes are started by default.
Contents of the deployment
Alfresco Content Services deployed via
docker-compose or Kubernetes contains the following:
- Alfresco Repository, with:
1.1. Alfresco Share Services
1.2. Alfresco Office Service (AOS) AMP
1.3. Alfresco vti-bin war - helps with AOS integration
1.4. Alfresco Google Docs Repo AMP
- Alfresco Share, with:
2.1 Alfresco Google Docs Share AMP
- A Postgres DB
- Alfresco Search Services (Solr6)
- Alfresco Transform Service
- Alfresco Digital Workspace
- Deploying with Helm charts on AWS using Kops
- Deploying with Helm charts on AWS using EKS
- Deploying with Helm charts using Minikube
- Deploying using Docker Compose
- Customizing your deployment
The Helm charts in this repository provide a PostgreSQL database in a docker container and do not configure
any logging. This design has been chosen so that they can be installed in a Kubernetes cluster without
changes and are still flexible to be adopted to your actual environment.
For your environment, you should use these charts as a starting point and modify them so that ACS integrates into your infrastructure. You typically want to remove the PostgreSQL container and connect the cs-repository directly to your database (might require custom images to get the required JDBC driver in the container). Another typical change would be the integration of your company-wide monitoring and logging tools.
- See alternative commands and start up tutorial with AWS support
- Tips and tricks for working with Kubernetes and Alfresco Content Services.
- The images downloaded directly from Docker Hub, or Quay.io are for a limited trial of the Enterprise version of Alfresco Content Services that goes into read-only mode after 2 days. Request an extended 30-day trial at https://www.alfresco.com/platform/content-services-ecm/trial/docker
- You'll need your Quay.io account credentials to access the Docker images. If you don't already have these credentials, contact Alfresco Support.