Freifunk-Rhein-Sieg/zammad-docker-compose
3
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
Zammad Docker images for docker-compose
391 Commits 16 Branches 19 Tags 728 KiB
Shell 100%
v8.0.0
Go to file
André Bauer 87e8b49794
update zammad to 5.3.0 (#313) 
* update zammad to 5.3.0

* update dependencies

Signed-off-by: André Bauer <andre.bauer@staffbase.com>

Signed-off-by: André Bauer <andre.bauer@staffbase.com>
2022-11-22 18:59:50 +01:00
.examples/proxy update docker images & ci (#276) 2022-04-25 23:13:34 +02:00
.github add release drafter, remove container & rework ci (#309) 2022-11-08 12:49:04 +01:00
scripts update zammad & components (#307) 2022-11-04 19:30:32 +01:00
.env update zammad to 5.3.0 (#313) 2022-11-22 18:59:50 +01:00
.gitignore switched to slim/alpine images 2017-01-11 20:34:49 +01:00
docker-compose.override-local.yml update zammad & components (#307) 2022-11-04 19:30:32 +01:00
docker-compose.override.yml update docker images & ci (#276) 2022-04-25 23:13:34 +02:00
docker-compose.yml update zammad to 5.3.0 (#313) 2022-11-22 18:59:50 +01:00
LICENSE moved to dockerhub images 2017-01-05 20:10:08 +01:00
rancher-compose.yml update docker images & ci (#276) 2022-04-25 23:13:34 +02:00
README.md adjust readme and docker image path (#310) 2022-11-08 16:08:16 +01:00

README.md

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 case for this repository

This repository is meant to be the starting point for somebody who likes to use dockerized multi-container Zammad in production.

Getting started with zammad-docker-compose

Learn more on Zammads documentation

Upgrading

For upgrading instrcutions see our Releases.

Please be aware that the zammad-cocker-compose repository versions and tags don't match the Zammad container tags!

Status

ci-remote-image Docker Pulls

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, it's volume and links to it.