Commit b8384634 authored by Pepijn Boers's avatar Pepijn Boers
Browse files

Update readme

parent dea7f9c1
......@@ -60,7 +60,7 @@ Since the second server works from a subdirectory, we have to add this line to m
proxy_uri_header = 1
```
JS tracking requests go to `/matomo.php`. We use the nginx (mirror module)[ngx_http_mirror_module] to duplicate the request and send it to our second server as well (only the original request gets a response). We have to adjust our proxy header again to store the client's original IP.
JS tracking requests go to `/matomo.php`. We use the nginx [mirror module](ngx_http_mirror_module) to duplicate the request and send it to our second server as well (only the original request gets a response). We have to adjust our proxy header again to store the client's original IP.
<img src="img/setup/proxy_mirror.png" alt="Request mirror" width="650"/>
......@@ -87,7 +87,7 @@ location = /mirror {
}
```
In order to let matomo know it is behind a reverse proxy we have to add some lines to the `config/config.ini.php` file in both installations, see this (faq)[https://matomo.org/faq/how-to-install/faq_98/]. Also we can assume our request are secure, because the connection client-proxy is over https, see illustration below.
In order to let matomo know it is behind a reverse proxy we have to add some lines to the `config/config.ini.php` file in both installations, see this [faq](https://matomo.org/faq/how-to-install/faq_98/). Also we can assume our request are secure, because the connection client-proxy is over https, see illustration below.
<img src="img/setup/reverse_proxy.png" alt="Reverse proxy setup" width="650"/>
......@@ -106,7 +106,7 @@ The matomo servers depend on a:
- Config file: `config/config.ini.php`
- Plugin folder: `plugins`
Both servers, databases and the single proxy server live in their individual docker container and are created, started and managed by `docker-compose`. The exact setup can be found in (docker-compose.yml)[docker-compose.yml] and is started/stopped with:
Both servers, databases and the single proxy server live in their individual docker container and are created, started and managed by `docker-compose`. The exact setup can be found in [docker-compose.yml](docker-compose.yml) and is started/stopped with:
```
docker-compose up -d
......@@ -115,4 +115,4 @@ docker-compose stop
```
Note: The warning: `(skip warning) mbind: Operation not permitted` is silenced using (this)[https://stackoverflow.com/a/55706057] stack overflow suggestion. The problem is explained (here)[https://github.com/docker-library/mysql/issues/422#issue-320548753]
\ No newline at end of file
Note: The warning: `(skip warning) mbind: Operation not permitted` is silenced using [this](https://stackoverflow.com/a/55706057) stack overflow suggestion. The problem is explained [here](https://github.com/docker-library/mysql/issues/422#issue-320548753)
\ No newline at end of file
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment