Gitter is not intended to be a replacement for Mattermost, Slack or other team collaboration tools. We see Gitter as a community instead.
As such, we're not expecting to see a huge uptake of on-site installations, so the list of required services (es, neo etc) is big compared to other products focused on on-prem.
We're hoping that our users will contribute to the main site, Gitter.im.
Obviously, we're also totally happy with users running their own Gitter installations but, while we would like it to be easy, ease-of-installation of a production instance is not a goal currently.
Going forward, I agree that we could offer a more production-like docker-compose setup and/or Kubernetes Helm Charts.
ok but doesn't it behoove you anyway to have e.g. dockerfile and/or ansible roles for dev/staging environments?
We use ansible for provisioning beta/staging and production. We have yet to open source the ansible repository but, since we're switching to GitLab CI/CD, the deployment process will soon be publicly accessible - even for production.
1: https://gitlab.com/gitlab-org/gitter/webapp/merge_requests/1... so that