self-hosted/matrix-docker-ansible-deploy
1
0
Fork 0
mirror of https://github.com/spantaleev/matrix-docker-ansible-deploy.git synced 2024-12-12 08:43:55 +02:00
Code Issues Releases Activity
ceba99eed3
matrix-docker-ansible-deploy/examples/apache
History
Slavi Pantaleev 9a251e4e46 Remove some more references to localhost 
Continuation of 1f0cc92b33.

As an explanation for the problem:
when saying `localhost` on the host, it sometimes gets resolved to `::1`
and sometimes to `127.0.0.1`. On the unfortunate occassions that
it gets resolved to `::1`, the container won't be able to serve the
request, because Docker containers don't have IPv6 enabled by default.

To avoid this problem, we simply prevent any lookups from happening
and explicitly use `127.0.0.1`.
2019-02-05 11:11:28 +02:00
..
matrix-riot-web.conf Remove some more references to localhost 2019-02-05 11:11:28 +02:00
matrix-synapse.conf Remove some more references to localhost 2019-02-05 11:11:28 +02:00
README.md Update own-webserver guide and add sample Apache configuration 2019-02-01 16:58:11 +02:00

README.md

Apache reverse-proxy

This directory contains sample files that show you how to do reverse-proxying using Apache.

This is for when you wish to have your own Apache webserver sitting in front of Matrix services installed by this playbook. See the Using your own webserver, instead of this playbook's nginx proxy documentation page.

To use your own Apache reverse-proxy, you first need to disable the integrated nginx server. You do that with the following custom configuration (inventory/matrix.<your-domain>/vars.yml):

matrix_nginx_proxy_enabled: false

You can then use the configuration files from this directory as an example for how to configure your Apache server.

NOTE: this is just an example and may not be entirely accurate. It may also not cover other use cases (enabling various services or bridges requires additional reverse-proxying configuration).