Support for more DNS-01 autocert providers when using public containers

[stancubed]

For those of us who are attempting to get this set up using a public registry like Docker Hub or someplace, we don't have to option of editing autocert.go and rebuilding the app to get something like Porkbun to work. The instructions provided don't address that.

Is there a way to get alternate DNS-01 providers to work without rebuilding the app and creating a new container or is there a more generic way to implement this?

[yusing]

You can do git clone, move your current config into it, modify compose.yml into this:

services:
  app:
    ...
    build: .

No worries, now I'll make it for you. I will figure out a way to make this easier.

[stancubed]

Right I use Portainer, so it's more difficult because it's much more difficult to git clone a repo and build the service and container locally. I think if there was a way to configure the provider in a config file, that would provide people with a lot more options.

[yusing]

Actually I can just add all the available options on lego, but I do not have access to those platforms.

When anything wrong happened, the responsibility comes to me and I have no way to fix it. That's why I left the testing side to users.

[yusing]

Done, https://github.com/yusing/go-proxy/releases/tag/0.9.6

Let me know it works

[stancubed]

You're fantastic I'm going to test this weekend and let you know!

[yusing]

Hi, have you tried it out yet? Does it work for you?