linkonoid / caddy-dyndns Goto Github PK

Support for Digital Ocean shouldn't be too hard since they have a Go library and it's fairly widely used, so I think it would be appreciated.

Currently there's no support for updating the AAAA record. I'd be happy to implement the required changes myself unless somebody is already working on it.

Sorry to post in issues, but a GoDaddy dyndns would be great. There is already a GoDaddy DNS TLS plugin, so hopefully will be easy enough to add if you have time.

https://desec.io/ is awesome and has a pretty good featurefull REST api: https://desec.readthedocs.io/en/latest/dns/domains.html

It would be great if you could support it.

Hello.
I'm trying to start the plugin but nothing works, please help me.
I downloaded the caddy using this link https://caddyserver.com/download/windows/amd64?plugins=dyndns&license=personal
Caddy version 0.10.12
The plugin appears in the list of installed ones, but when I try to use it the error occurs.
Error during parsing: Unknown directive 'dyndns'
Caddyfile taken from here https://github.com/linkonoid/caddy-dyndns/blob/master/Caddyfile

Caddy's import path (and Go module name) has changed from

github.com/mholt/caddy

to

github.com/caddyserver/caddy

Unfortunately, Go modules are not yet mature enough to handle a change like this (see https://golang.org/issue/26904 - "haven't implemented that part yet" but high on priority list for Go 1.14) which caught me off-guard. Using Go module's replace feature didn't act the way I expected, either. Caddy now fails to build with plugins until they update their import paths.

I've hacked a fix into the build server, so downloading Caddy with your plugin from our website should continue working without any changes on your part, for now. However, please take a moment and update your import paths, and do a new deploy on the website, because the workaround involves ignoring module checksums and performing a delicate recursive search-and-replace.

I'm terribly sorry about this. I did a number of tests and dry-runs to ensure the change would be smooth, but apparently some unknown combination of GOPATH, Go modules' lack of maturity, and other hidden variables in the system or environment must have covered up something I missed.

This bash script should make it easy (run it from your project's top-level directory):

find . -name '*.go' | while read -r f; do
	sed -i.bak 's/\/mholt\/caddy/\/caddyserver\/caddy/g' $f && rm $f.bak
done

We use this script in the build server as part of the temporary workaround.

Let me know if you have any questions! Sorry again for the inconvenience.