self-hosted/Mailu
1
0
Fork 0
mirror of https://github.com/Mailu/Mailu.git synced 2025-05-21 22:33:16 +02:00
Code Issues Releases Activity

Fix the links

Browse Source
This commit is contained in:
Florent Daigniere 2021-08-27 18:42:11 +02:00
parent 9e306bf255
commit d65993886a
1 changed files with 7 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
docs/reverse.rst
View File

@ -7,9 +7,9 @@ In such a configuration, one would usually run a frontend reverse proxy to serve
There are basically three options, from the most to the least recommended one: There are basically three options, from the most to the least recommended one:
- have Mailu Web frontend listen locally and use your own Web frontend on top of it - `have Mailu Web frontend listen locally and use your own Web frontend on top of it`_
- use ``Traefik`` in another container as central system-reverse-proxy - `use Traefik in another container as central system-reverse-proxy`_
- override Mailu Web frontend configuration - `override Mailu Web frontend configuration`_
All options will require that you modify the ``docker-compose.yml`` file. All options will require that you modify the ``docker-compose.yml`` file.
@ -258,3 +258,7 @@ You can also download the example configuration files:
- :download:`compose/traefik/docker-compose.yml` - :download:`compose/traefik/docker-compose.yml`
- :download:`compose/traefik/traefik.toml` - :download:`compose/traefik/traefik.toml`
.. _have Mailu Web frontend listen locally and use your own Web frontend on top of it: #have-mailu-web-frontend-listen-locally
.. _use Traefik in another container as central system-reverse-proxy: #traefik-as-reverse-proxy
.. _override Mailu Web frontend configuration: #override-mailu-configuration