Caddy add-package hangs when trying to add lego-deprecated

[ryanburnette]

1. The problem I’m having:

I am trying to use caddy add-package to add lego-deprecated. I can add other packages, but with this one it hangs on requesting build.

2. Error messages and/or full log output:

app@myhost ~/p/api (main) [1]> caddy add-package github.com/caddy-dns/lego-deprecated
2023/05/12 03:28:27.569	INFO	this executable will be replaced	{"path": "/home/app/.local/opt/caddy-v2.6.4/bin/caddy"}
2023/05/12 03:28:27.569	INFO	requesting build	{"os": "linux", "arch": "amd64", "packages": ["github.com/caddy-dns/digitalocean", "github.com/caddy-dns/lego-deprecated"]}

3. Caddy version:

2.6.4

4. How I installed and ran Caddy:

Installed using webinstall.dev/caddy

a. System environment:

ubuntu 20.04
amd64

b. Command:

caddy add-package github.com/caddy-dns/lego-deprecated

c. Service/unit/compose file:

N/A

d. My complete Caddy config:

N/A

5. Links to relevant resources:

[francislavoie]

That package is huge, it adds a lot of dependencies, hence why it’s deprecated. It continually brings the build server to its knees.

I suggest you build it on your own hardware with xcaddy instead.

Build from source - Caddy Documentation

[matt (Matt Holt)]

This reminds me it’s probably time to remove that plugin from our website. It’s too expensive to build on our limited infrastructure and our newer, lighter caddy-dns packages support about 50 providers now, with more continually being contributed by the community.

[ryanburnette]

I can rebuild it with xcaddy. Np. My reason for using lego is that dnsimple isn’t present in the current caddy-dns libs. Is there anything holding back caddy-dns/dnsimple other than nobody has written and tested it?

[francislavoie]

Yeah I think nobody’s written it yet. You could be the one to do it!

Writing new DNS provider modules for Caddy

Caddy 2 uses a new set of interfaces for its DNS provider APIs. While there is a shim to use all the existing old ones for now, the new APIs offer better performance, leaner builds, and more capabilities. We want all providers to be ported over to the new APIs as soon as possible. Since I do not have accounts with all DNS providers in the world, it’s up to the community to migrate to the new APIs and to maintain their implementations. This post will show you how! For what it’s w…

[matt (Matt Holt)]

Yeah, as Francis said it hasn’t been written yet – but DNSimple is pretty fantastic, so I imagine their API is good. You should have no problem doing it I hope

Here’s the relevant issue requesting it:

DNSimple Provider