Added MASH and docker options

Added the link to mash and the compatibility adjustments.

Mentioned the prefered method with docker containers.

Some rephrasing to make clear, the intended guide ios for reverse proxying non-docker services.

docs/configuring-playbook-traefik.md

@@ -35,7 +35,7 @@ devture_traefik_dashboard_basicauth_user: YOUR_USERNAME_HERE
 devture_traefik_dashboard_basicauth_password: YOUR_PASSWORD_HERE
 ```
 
-**WARNING**: enabling the dashboard on a hostname you use for something else (like `matrix_server_fqn_matrix` in the configuration above) may cause conflicts. Enabling the Traefik Dashboard makes Traefik capture all `/dashboard` and `/api` requests and forward them to itself. If any of the services hosted on the same hostname requires any of these 2 URL prefixes, you will experience problems. So far, we're not aware of any playbook services which occupy these endpoints and are likely to cause conflicts.
+**WARNING**: Enabling the dashboard on a hostname you use for something else (like `matrix_server_fqn_matrix` in the configuration above) may cause conflicts. Enabling the Traefik Dashboard makes Traefik capture all `/dashboard` and `/api` requests and forward them to itself. If any of the services hosted on the same hostname requires any of these 2 URL prefixes, you will experience problems. So far, we're not aware of any playbook services which occupy these endpoints and are likely to cause conflicts.
 
 ## Additional configuration
 
@@ -49,9 +49,15 @@ devture_traefik_configuration_extension_yaml: |
     dashboard: true
 ```
 
-## Hosting another server behind traefik and terminate SSL
+## Reverse-proxying another service behind Traefik
 
-If you want to host another webserver that is reachable via `my_fancy_website.mydomain.com` from the internet and by `https://<internal webserver IP address>:<internal port>` from inside your network, you can make traefik route the traffic to the correct one.
+The preferred way to reverse-proxy additional services behind Traefik would be to add the service as another container, configure the container with the corresponding traefik labels, and add it to the `traefik` network. Some services are also already available via the compatible [mash-playbook](https://github.com/mother-of-all-self-hosting/mash-playbook), but take a look at the minor [interoperability adjustments](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/interoperability.md).
+
+However, if your service is not available as a docker container or runs on another machine, the following configuration mighht be what you are looking for.
+
+## Reverse-proxying another HTTP/HTTPS service behind Traefik without using docker
+
+If you want to host another webserver that is reachable via `my_fancy_website.mydomain.com` from the internet and via `https://<internal webserver IP address>:<internal port>` from inside your network, you can make traefik reverse-proxy the traffic to the correct host.
 
 Prerequisites: DNS and routing for the domain `my_fancy_website.mydomain.com` need to be set up correctly to reach your traefik instance.
 
@@ -67,7 +73,7 @@ devture_traefik_configuration_extension_yaml: |
       filename: ""
 ```
 
-If you are using a self signed certificate on your webserver, you can tell traefik to trust your own backend servers by adding more configuration to the static configuration file:
+If you are using a self signed certificate on your webserver, you can tell traefik to trust your own backend servers by adding more configuration to the static configuration file. If you do so, bear in mind the security implications of disabling the certificate validity checks towards your back end.
 
 ```yaml
 # We enable all config files in the /config/ folder to be loaded and
@@ -81,7 +87,8 @@ devture_traefik_configuration_extension_yaml: |
     insecureSkipVerify: true
 ```
 
-Then you have to add a new dynamic configuration file for traefik that contains the actual information of the server using the `aux_file_definitions` variable. In this example, we will terminate SSL at the traefik instance and connect to the other server via HTTPS. Traefik will now take care of managing the certificates. 
+
+Next, you have to add a new dynamic configuration file for traefik that contains the actual information of the server using the `aux_file_definitions` variable. In this example, we will terminate SSL at the traefik instance and connect to the other server via HTTPS. Traefik will now take care of managing the certificates. 
 
 ```yaml
 aux_file_definitions:
@@ -102,9 +109,9 @@ aux_file_definitions:
 ```
 Changing the url to HTTP would allow to connect to the server via HTTP.
 
-## Hosting another server behind traefik but do not terminate SSL
+## Reverse-proxying another service behind Traefik without terminating SSL
 
-If we do not want to terminate SSL on the traefik instance, we need to adjust the static configuration as above. Afterwards, we need to adjust the dynamic configuration file as follows:
+If you do not want to terminate SSL on the traefik instance, you need to adjust the static configuration in the same way as in the previous chapter in order to be able to add our own dynamic configuration files. Afterwards, you can enter the following configuration to the dynamic configuration file:
 
 ```yaml
 aux_file_definitions:
@@ -125,4 +132,6 @@ aux_file_definitions:
 ```
 Changing the url to HTTP would allow to connect to the server via HTTP.
 
-This configuration might lead to problems or need additional steps when a certbot behind traefik also tries to manage Let's Encrypt certificates, as traefik captures all traffic to ```PathPrefix(`/.well-known/acme-challenge/`)```. 
+With these changes, all TCP traffic will be reverse-proxied to the target system. 
+
+**WARNING**: This configuration might lead to problems or need additional steps when a certbot behind traefik also tries to manage Let's Encrypt certificates, as traefik captures all traffic to ```PathPrefix(`/.well-known/acme-challenge/`)```.