On a server which has IPv6 configured, `sudo certbot --nginx` would fail because certbot looks for both A and AAAA DNS records, and if AAAA (IPv6) is found it uses that.
By adding:
```
listen 80;
listen [::]:80;
```
issue #22 is solved. Servers which have only IPv4 configured will continue working normally.
By switching to the latest or 13 version, the plausible_db container will no more complain about the wrong postgres version and shut down. This resolved my error, when i implemented this docker-compose into my own docker-compose.
Based on caddy-gen
This will start a reverse proxy on port 80 and 443, which proxies
to the plausible container. Note that it will clash with any
existing reverse proxies on the host machine
This is done in preparation for adding reverse-proxy configurations
Unfortunately a later docker-compose file cannot *remove* a port
binding, so it has to be removed in the root file.
If there is interest, the 80:8000 binding can be re-added in a
new docker-compose overwrite file.
I got confused why I couldn't log in even though the credentials were correct.
Turns out you're supposed to remove the brackets around the env variables - I didn't knew that. I think this will prove less confusing
