nginx-proxy-automation VS devcontainers-mongodb-replica-set-with-docker

I use this repo as a reverse proxy: https://github.com/evertramos/nginx-proxy-automation/tree/main/docs

https://github.com/evgeniy-khist/letsencrypt-docker-compose https://github.com/evertramos/nginx-proxy-automation

I have this NGINX proxy companion installed on my server, so, in order to have AdGuard as a Docker container I made the following docker-compose.yml working file:

For my nginx proxy using lets encrypt I used this resouce and wordpress was this.

This setup was working until I tried changing from a deprecated Nginx proxy manager to a more up-to-date one, at the same time as setting up Yacht. Subdomains of the working URL also work, no domains/subdomains of the non-working URLs work.

And here you can find various real world examples: https://github.com/evertramos/nginx-proxy-automation#other-projects-using-nginx-proxy

I am using Docker to host Matomo, get Let's Encrypt SSL certificates and run Nginx as a reverse proxy. To make things really easy, we can setup the awesome evertramos/nginx-proxy-automation project. Follow the instructions in the README to setup the containers via Docker. This will automatically create a Docker network called webproxy.

A flaw in that setup, was that although clients could connect to stand-alone nodes of the replica set, they could not connect to the replica set as a whole, as reported by this issue on the github repository.

Here we have specified that the docker compose will be using the .env file to read environment variables and inject them into the container. This allows us to specify that the database's root username/password and initial database name to be picked up from specific environment variables. In my github repository, I have provided a sample env file that you can use to create your own .env file. Contents of the sample env file looks like this: