Deployment descriptors pull together Alfresco Content Services (Enterprise)
Clone or download
montgolfiere Merge pull request #110 from Alfresco/fix/ATS-198_ACE-5893_fix_1Mb_limit
ATS-198 : ACE-5893: Files bigger than 1MB can not be uploaded via multipart API
Latest commit b59ae98 Nov 19, 2018

README.md

Alfresco Content Services Deployment

Contributing guide

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:

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-repository nodes are started by default.

Contents of the deployment

Alfresco Content Services deployed via docker-compose or Kubernetes contains the following:

  1. 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
  2. Alfresco Share, with:
    2.1 Alfresco Google Docs Share AMP
  3. A Postgres DB
  4. Alfresco Search Services (Solr6)
  5. Alfresco Transform Service
  6. Alfresco Digital Workspace

Deployment options

Production environments

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.

Other information