Zammad Coolify

This repository was created to allow the easy deployment of Zammad Community (an open source helpdesk/ticketing tool) through the Coolify platform. For now, it only works if Traefik is configured as the reverse proxy of the Coolify system (which it should be by default). The relevant environment variables "NGINX_SERVER_SCHEME" and "RAILS_TRUSTED_PROXIES" are configured to work with the default Coolify configuration.

Deployment

To deploy this image with Coolify, simply create a new Resource from a public git repository (this). Make sure to select "Docker Compose" as the "Build Pack" and change the default "docker-compose.yaml" to "docker-compose.yml" (without the a). The default branch used by Coolify is "main". This cannot be changed in the initial setup, thus first create the resource, then head to "Source" and change the git branch to "master". If you then reload your Coolify interface, the Docker Compose file should be fetched correctly. You can then apply your own customizations such as the "Domains for Zammad Nginx", which are your publicly facing domains for the helpdesk (these will be picked up by traefik and relayed correctly).

Welcome to Zammad

Zammad is a web based open source helpdesk/ticket system with many features to manage customer communication via several channels like telephone, facebook, twitter, chat and emails. It is distributed under the GNU AFFERO General Public License (AGPL). Do you receive many emails and want to answer them with a team of agents? You're going to love Zammad!

Use cases

This repository is the starting point if you want to:

• deploy Zammad in a containerized production environment
• test the current stable or develop versions of Zammad

Getting started

Learn more on Zammad’s documentation

Upgrading

For upgrading instructions see our Releases.

Status

Using a reverse proxy

In environments with more then one web applications it is necessary to use a reverse proxy to route connections to port 80 and 443 to the right application. To run Zammad behind a reverse proxy, we provide docker-compose.proxy-example.yml as a starting point.

1. Copy ./.examples/proxy/docker-compose.proxy-example.yml to your own configuration, e.g. ./docker-compose.prod.yml cp ./.examples/proxy/docker-compose.proxy-example.yml ./docker-compose.prod.yml
2. Modify the environment variable VIRTUAL_HOST and the name of the external network in ./docker-compose.prod.yml to fit your environment.
3. Run docker-composer commands with the default and your configuration, e.g. docker compose -f docker-compose.yml -f docker-compose.prod.yml up -d

See .examples/proxy/docker-compose.yml for an example proxy project.

Like this, you can add your docker-compose.prod.yml to a branch of your Git repository and stay up to date by merging changes to your branch.

Using Rancher

RANCHER_URL=http://RANCHER_HOST:8080 rancher-compose --env-file=.env up

Running without Elasticsearch

Elasticsearch is an optional, but strongly recommended dependency for Zammad. More details can be found in the documentation. There are however certain scenarios when running without Elasticsearch may be desired, e.g. for very small teams, for teams with limited budget or as a temporary solution for an unplanned Elasticsearch downtime or planned cluster upgrade.

Elasticsearch is enabled by default in the example docker-compose.yml file. It is also by default required to run the "zammad-init" command. Disabling Elasticsearch is possible by setting a special environment variable: ELASTICSEARCH_ENABLED=false for the zammad-init container and removing all references to Elasticsearch everywhere else: the zammad-elasticsearch container, its volume and links to it.