zammad-docker-compose/README.md

53 lines
2.1 KiB
Markdown
Raw Normal View History

# Welcome to Zammad
2016-12-17 11:10:51 +00:00
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
2018-02-05 19:20:23 +00:00
License (AGPL). Do you receive many e-mails and want to answer them with a team of agents?
2016-12-17 11:10:51 +00:00
You're going to love Zammad!
## What is zammad-docker-compose repo for?
2016-12-17 11:10:51 +00:00
2017-01-09 21:56:23 +00:00
This repo is meant to be the starting point for somebody who likes to use dockerized multi-container Zammad in production.
2016-12-17 11:10:51 +00:00
## Getting started with zammad-docker-compose
2017-01-09 14:11:53 +00:00
https://docs.zammad.org/en/latest/install-docker-compose.html
## Build Status
[![Build Status](https://travis-ci.org/zammad/zammad-docker-compose.svg?branch=master)](https://travis-ci.org/zammad/zammad-docker-compose)
2017-11-13 08:57:22 +00:00
2017-11-13 08:57:22 +00:00
## 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`
1. Modify the environment variable `VIRTUAL_HOST` and the name of the external network in `./docker-compose.prod.yml` to fit your environment.
1. 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
2020-02-19 22:14:14 +00:00
## Upgrading
We recently updated the Elasticsearch image from 5.6 to 7.6.
As there is no direct upgrade path we have to delete all Elasticsearch indicies and rebuild them.
To do this start docker-compose like:
```
docker-compose up -e ELASTICSEARCH_PURGE=true
```