Set up Go vanity imports for kode.dataverket.org

Context

All Go modules use kode.dataverket.org as their canonical import path (e.g. kode.dataverket.org/docs-builder, kode.dataverket.org/dvce). Until kode.dataverket.org is live, this works for local builds but go get from the public internet cannot resolve these paths.

When kode.dataverket.org comes online, it must serve Go vanity import meta tags so the Go toolchain can discover the backing Git repository.

What to configure

The Forgejo instance at kode.dataverket.org needs to respond to ?go-get=1 queries with the correct <meta name="go-import"> tag.

For each repository the response at https://kode.dataverket.org/<repo>?go-get=1 must include:

<meta name="go-import" content="kode.dataverket.org/<repo> git https://kode.dataverket.org/<repo>.git">

Forgejo built-in support

Forgejo (and Gitea) serve the go-import meta tag automatically for any repository when the request includes ?go-get=1. If the Forgejo instance hostname matches the module path prefix (kode.dataverket.org), no extra configuration is needed — it works out of the box.

Verification

After the instance is live, verify with:

go list -m -json kode.dataverket.org/docs-builder@latest
go list -m -json kode.dataverket.org/dvce@latest

Both should resolve without errors and show the correct repository URL.

Current modules