* Honor ELASTICSEARCH_SCHEMA when accessing Elasticsearch in the Zammad entrypoint
It defaults to http so it's completely backwards-compatible. In case it's https I disabled
verification in the curl command via -k.
* Add ELASTICSEARCH_SSL_VERIFY environment variable in Zammad entrypoint
Setting it to "false" will skip TLS verification when interacting with Elasticsearch.
* Add default value for ELASTICSEARCH_SSL_VERIFY env variable
- switched back to postgresql 9.6 (10.x with next release)
- switched back to zammad image repos
- switched back to stable branch (dalli gem now included)
- replaced wget with curl
- made zammad image smaller by using tar.gz install instead of git clone
- moved sed commands to entrypoint
- added variables to entrypoint to set used servers dynamically
- added kubernetes backup cronjob
- added postgresql volume to compose file
- write nginx logs to stdout & stderr
- create zammad user & group manually with uid/gid 1000
- added memcached container (currently develop branch needed)
- put all zammad services in one kubernetes pod to be able to use empty dir volume for tmp
- switched to kubernetes deployments
- switched to ReadWriteOnce kubernetes volume claims
- added init container to elasticsearch & zammad kubernetes deployments
- added IMAGE_REPO var for docker compose to .env file
- run nginx from zammad container (preparation for stateless updates)
- removed docker-compose-build.yml
- use private docker repos in compose & kubernetes
- change compose volume names
