Skip to content

Latest commit

 

History

History
44 lines (35 loc) · 2.54 KB

customising-deployment.md

File metadata and controls

44 lines (35 loc) · 2.54 KB

Customising your deployment

Alfresco Content Services is composed of the following images:

  1. alfresco-content-repository | tags
  2. alfresco-pdf-renderer | tags
  3. alfresco-imagemagick | tags
  4. alfresco-libreoffice | tags
  5. alfresco-tika | tags
  6. alfresco-share | tags
  7. alfresco-search-services | tags
  8. postgres | tags

For Docker Compose usage, edit the image tags in the docker-compose.yml file.

For Helm charts usage, edit the image tags in the values.yaml file.

project
│
└───docker-compose
│   │
│   └──docker-compose.yml
│
└───helm
    │  
    └───alfresco-content-services
        │
        └───values.yaml

Note:

  • Use the recommended image tags, as not all combinations may work.
  • You can modify the values provided in values.yaml when deploying the Helm chart. For example, you can run:
helm install alfresco-incubator/alfresco-content-services --set repository.image.tag="yourTag" --set share.image.tag="yourTag"
  • You can run eval $(minikube docker-env) to switch to your Minikube Docker environment on Mac OS X.

K8s deployment customization guidelines

All the customizations (including major configuration changes) should be done inside the Docker image, resulting in the creation of a new image with a new tag. This approach allows changes to be tracked in the source code (Dockerfile) and rolling updates to the deployment in the K8s cluster.

The helm chart configuration customization should only include environment-specific changes (for example DB server connection properties) or altered Docker image names and tags. The configuration changes applied via "--set" will only be reflected in the configuration stored in k8s cluster, a better approach would be to have those in VCS.