annixa / docker-nginx-letsencrypt-proxy Goto Github PK

When adding domains to the LE_DOMAIN env variable, you may be prompted to expand and replace the existing certificate with a new one.

Add the --expand flag to automatically accept the expansion.

Allow for a LE_ENABLED mode that is:

• true by default
• if false does not attempt to request certificates and simply uses fake certs

Past overdue for updating cipher suites. Maybe one day this could be automated.

Process would check for updated cipher suites and regenerate webapp.conf then restart nginx.

If a user provides:

• an env AWS_KEY
• an env AWS_SECRET
• and their Route 53 has a zone associated with the root of the domain(s) provided in LE_DOMAIN

then automatically update A (and CNAME?) records to match the current container.

Considerations:

• Parsing tlds
• The apex of a domain cannot have a CNAME

    location / {
    	return 301 htpts://$host$request_uri$PROXY_PORT_FWD;
    }

should be:

    location / {
    	return 301 https://$host$request_uri$PROXY_PORT_FWD;
    }

Checking every hour is too much!

Allow the user to provide some kind of scheduling configuration to set when the nginx server should be restarted if the certificates have been updated, recently.

The README should include an example docker-compose.yml to demonstrate its usage.

Docker Hub is trying to detect *test.yml in the source code to determine whether there's a test sequence for the project.

I was not expecting this, so the build failed :(

Change the name to *example.yml

Currently, a server has to generate its dhparams.pem every time the container starts.

Fix it to store the dhparams.pem in /etc/letsencrypt and copy it in like other certificates...