Since I now consider issue #2 as expected behavior, I guess the caddy-dns/all-inkl module is ready for prime time! For this, there is one more little thing:
The Caddy docs state, that one can use the command "caddy upgrade" to easily update custom builds. However, when using this, an error occurs, complaining that caddy-dns/all-inkl is "not a registered Caddy module".
~# caddy upgrade
INFO: requesting build {"os": "linux", "arch": "amd64", "packages": ["github.com/caddy-dns/all-inkl@v0.2.4"]}
Error: download failed: download failed: HTTP 400: github.com/caddy-dns/all-inkl is not a registered Caddy module package path (id=1323d8a5-eb57-4a84-9e95-7753ef8569de)
The docs further state, that this command again includes "all third-party plugins that are registered on the Caddy website". Since this error occurs, it seems that caddy-dns/all-inkl is not "officially" registered as a Caddy package. Exploring this Modules page, it can not be found – but I suspect it should be placed somewhere around dns.providers.*, like dns.providers.allinkl.
So, the question to you as the maintainer of this module: would you be willing to register your module as a Caddy package module?
I don’t know exactly how this would happen, I only found this and this, as a start. I suspect that the function "caddy.RegisterModule()" needs to be placed in the module’s code somewhere.
Hope you can figure this out; would be really helpful and keeps this module in line with the Caddy architecture.
Thanks a lot!
After this last step, everything should be done and finished.
Since I now consider issue #2 as expected behavior, I guess the caddy-dns/all-inkl module is ready for prime time! For this, there is one more little thing:
The Caddy docs state, that one can use the command "caddy upgrade" to easily update custom builds. However, when using this, an error occurs, complaining that caddy-dns/all-inkl is "not a registered Caddy module".
The docs further state, that this command again includes "all third-party plugins that are registered on the Caddy website". Since this error occurs, it seems that caddy-dns/all-inkl is not "officially" registered as a Caddy package. Exploring this Modules page, it can not be found – but I suspect it should be placed somewhere around dns.providers.*, like dns.providers.allinkl.
So, the question to you as the maintainer of this module: would you be willing to register your module as a Caddy package module?
I don’t know exactly how this would happen, I only found this and this, as a start. I suspect that the function "caddy.RegisterModule()" needs to be placed in the module’s code somewhere.
Hope you can figure this out; would be really helpful and keeps this module in line with the Caddy architecture.
Thanks a lot!
After this last step, everything should be done and finished.