Empty github.com/caddy-dns/transip even though there is a community implementation

[Nasho]

1. The problem I’m having:

I’m trying to add libdns/transip to my caddy installation as a dns provider. There are some community built ones already. See:

GitHub - zjean/transip

Can't retrieve ssl certificate with my transip provider

1. The problem I’m having: I am trying to setup DNS ACME challenge for my domain hosted at Transip. I built a module for it: GitHub - zjean/transip I built my own docker image: ARG CADDY_VERSION=2.6.4 FROM caddy:${CADDY_VERSION}-builder AS builder RUN xcaddy build \ --with github.com/lucaslorentz/caddy-docker-proxy/v2 \ --with github.com/zjean/transip FROM caddy:${CADDY_VERSION} COPY --from=builder /usr/bin/caddy /usr/bin/caddy CMD ["caddy", "docker-proxy"] Caddy spits out an err…

However

GitHub - caddy-dns/transip: Caddy module: dns.providers.transip

Remains empty. Even though it seems the necessary changes where merged by zjean and mholt:

Fix transip

I don’t know how to tag the people involved, but it would be nice if somehow we could add this to the official list of dns providers.

[francislavoie]

FYI @matt

I think he created those repos for the person who would implement it but they never moved their code over to the libdns/caddy-dns namespace repos.

[Nasho]

Ok makes sense!

I tried to build caddy with xcaddy and adding this non official repo. But I’m still getting a similar error to @zjean from libdns/transip it seems. I tried 3 other community caddy dns provider shells around libdns/transip and they all give some form of nilpointer.

[matt (Matt Holt)]

Thanks, I opened an issue to see: Publish caddy-dns module · Issue #8 · libdns/transip · GitHub

[Nasho]

So, if there is no response I would be interested in trying to create my own version of the module / finding out what the issue is.

Looking at the trace it seems like the setupRepositories() results in a nilpointer for the Respository.

I read that I can do a xcaddy run within a local module to run caddy with that module enabled. Does this also work for the DNS modules?

[francislavoie]

@Nasho

I read that I can do a xcaddy run within a local module to run caddy with that module enabled. Does this also work for the DNS modules?

Yes it does.

The way DNS modules are designed is as two separate packages, one is the caddy config layer (and what you plug in typically) and the other is the libdns implementation. It’s done that way because DNS modules could be used without Caddy (e.g. with certmagic which is the library underlying Caddy for the ACME automation, for any other Go project to use). So you’d just need both set up (you can add a replace rule to your go.mod to point to your local copy of the libdns implementation).

[Nasho]

Ok, I will take a look into what’s going on then.

[Nasho]

@francislavoie @matt
Created it and it is working for me perfectly with a local build. Would love for it to become the main one, so I don’t have to custom build like this and others can use it