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 e-mails. It is distributed under the GNU AFFERO General Public License (AGPL). Do you receive many e-mails and want to answer them with a team of agents? You're going to love Zammad!
This repo is meant to be the starting point for somebody who likes to use dockerized multi-container Zammad in production.
https://docs.zammad.org/en/latest/install-docker-compose.html
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 revers proxy, we provide docker-compose.proxy-example.yml as a starting point.
- Copy
./.examples/proxy/docker-compose.proxy-example.ymlto your own configuration, e.g../docker-compose.prod.yml
cp ./.examples/proxy/docker-compose.proxy-example.yml ./docker-compose.prod.yml - Modify the environment variable
VIRTUAL_HOSTand the name of the external network in./docker-compose.prod.ymlto fit your environment. - 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.
Configuration for automated configuration of letsencrypt SSL certificates is in docker-compose.prod.yml.
The respective initial setup has to be done by executing the interactive script init-letsencrypt.sh on production. Make shure the variables at the beginning of the script are set correctly.
- RANCHER_URL=http://RANCHER_HOST:8080 rancher-compose --env-file=.env up