Project name change

[buchdag]

Following a discussion with the members of the nginx-proxy org (more info here: nginx-proxy/nginx-proxy#1304) we've agreed to rename this project, with the most probable choice being nginx-proxy/acme-companion.

My rationale for the renaming is:

• Docker aren't fond of project using "docker" in their name (that's why the image actual name is letsencrypt-nginx-proxy-companion while the GitHub repository name is docker-letsencrypt-nginx-proxy-companion), so we should as well remove it.
• now that the project is under the nginx-proxy org, that fact that it is a companion for nginx-proxy/nginx-proxy is kinda implied, so we can also remove it.
• as the project has evolved to support more ACME CAs than just Let's Encrypt (namely BuyPass and ZeroSSL), I feel like acme-companion would more accurately reflect the goal of the project and does not tie it to one specific provider's commercial name.

The would be combined with the image being pushed to and available from a new nginxproxy/acme-companion DockerHub registry (in addition to jrcs/letsencrypt-nginx-proxy-companion).

Comments are welcome.

[callmemagnus]

I think it's a good idea. The new proposed name is simpler.

[73]

Great choice! Thanks for all your work!

[jrd]

I second the idea.
Also if the docker hub image could be rebuild more often/automatically to fix common CVE/security issues. This container is very essential so it needs to be really up to date :-)

[adamkdean]

I think this is a good idea!

[buchdag]

@jrd what would be a sensible rebuild schedule to you ?

[buchdag]

Project name has been changed, docs update will follow.

[jrd]

@buchdag well about once or twice per month seems a good enough schedule to maintain security.

[buchdag]

@jrd rebuild and push of the default branch's last commit have been scheduled every Monday at 00:00 UTC (d56d1aa)