Zammad Docker images for docker-compose
Go to file
2018-11-04 23:09:19 +01:00
.examples/proxy Add documentation for proxy example 2017-11-13 09:57:22 +01:00
.github Added info text to avoid unnecessary issue creation. 2017-07-13 12:17:54 +02:00
containers update es to 5.6.12 2018-11-04 23:00:36 +01:00
hooks - switched to single zammad pod to get rid of nfs container in kubernetes 2017-12-02 12:58:46 +01:00
kubernetes Updated minikube ram 2017-12-08 14:52:02 +01:00
.env Set restart option with .env (#87) 2018-08-16 12:40:41 +02:00
.gitignore switched to slim/alpine images 2017-01-11 20:34:49 +01:00
.travis.yml changed docker login 2018-11-04 23:09:19 +01:00
docker-compose.override.yml set docker-compose version to 2 for rancher 2017-12-09 12:36:38 +01:00
docker-compose.yml Set restart option with .env (#87) 2018-08-16 12:40:41 +02:00
Dockerfile bumped version label to 1.2 2017-01-10 01:56:18 +01:00
LICENSE moved to dockerhub images 2017-01-05 20:10:08 +01:00
rancher-compose.yml added init container (installation / update)... (#2) 2017-11-26 21:25:57 +01:00
README.md Update README.md 2018-02-05 20:20:23 +01:00

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 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!

What is zammad-docker-compose repo for?

This repo 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

https://docs.zammad.org/en/latest/install-docker-compose.html

Build Status

Build 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 revers 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