Fix the Apache configuration in the Docker Compose page

[bsautel]

I deployed recently a Jitsi Meet instance via Docker Compose and exposed it behind an Apache reverse proxy and noticed a few issues in the documentation.

Here are some suggested improvements:

• Declaring ws proxies in a <Location> section does not work (it sounds like it works only for HTTP and not WebSocket). The ProxyPass [from] [to] syntax works, so I used it.
• Proxying /http-bind to the web container is not sufficient, the frontend for instance is not served. All the paths (so /) need to be proxied to the web container.
• Proxy to HTTP and not HTTPS

Regarding HTTP vs HTTPS, generally HTTPS won't work on localhost, so we use HTTP and WS (instead of WSS) to access the web container. That's consistent with this sentence extracted from the same document:

HTTP (not HTTPS) is also available (on port 8000, by default), but that's e.g. for a reverse proxy setup

I also explained how to configure the Docker Compose project do disable HTTPS and how to prevent the web container from binding to public ip addresses (which is not necessary when using a proxy).

This configuration works for my Jitsi Meet instance.

Note that I only fixed the Apache part but some of the of the issues I fixed seem to be also present for nginx, but I don't know it enough to fix them:

• It should proxy to HTTP and not HTTPS (no certificate on localhost). If this changes, the part regarding how to disable HTTPS in the web container I added should be shared between nginx and Apache.
• It should not only proxy the /http-bind requests to the web container but all of them (/).

Hope this will help to improve the Jitsi Meet handbook!

[saghul]

Thank you! @damencho can you also PTAL?