I don't fully understand yet, but this is my current understanding.
The nginx-proxy container has access to /certs, /html (for challenge from acme - automated certificate management environment), /vhost (for server containers), and /static and .../docker.sock (to know when new containers are connected to network).
The nginx-proxy-acme-companion runs acme.sh to issue a certificate from let's encrypt endpoint and issues challenge to nginx-proxy using /vhost and verified challenge in /html as well as storing the certificate in /certs.
Then when users send request from browser to my HOST aka mangastyle.lol, nginx-proxy will get certificate from /certs and send to browser to establish https connection.
I don't understand how certificate renewal will work, but the key is that the end goal is to get a certificate from let's encrypt endpoint.
I don't fully understand yet, but this is my current understanding.
The nginx-proxy container has access to /certs, /html (for challenge from acme - automated certificate management environment), /vhost (for server containers), and /static and .../docker.sock (to know when new containers are connected to network).
The nginx-proxy-acme-companion runs acme.sh to issue a certificate from let's encrypt endpoint and issues challenge to nginx-proxy using /vhost and verified challenge in /html as well as storing the certificate in /certs.
Then when users send request from browser to my HOST aka mangastyle.lol, nginx-proxy will get certificate from /certs and send to browser to establish https connection.
I don't understand how certificate renewal will work, but the key is that the end goal is to get a certificate from let's encrypt endpoint.