Go modules from this instance, over the module proxy protocol. Public ones. Log in to see your own.

module version repository released
go.bigb.es/shroud ~bigbes/shroud
sourcecraft.dev/bigbes/ftl-shape ~bigbes/game-prototype-ftl
sourcecraft.dev/bigbes/huntsman ~bigbes/huntsman
sourcecraft.dev/bigbes/lethe ~bigbes/lethe
git.sr.ht/~sircmpwn/core-go ~bigbes/core-go
go.bigb.es/sourcehut-dolt ~bigbes/sourcehut-dolt
go.bigb.es/cacher v0.2.2 ~bigbes/ci-cacher 2 months ago
sourcecraft.dev/bigbes/sr-ht-spec ~bigbes/sr-ht-spec
sourcecraft.dev/bigbes/sr-ht-dolt ~bigbes/sr-ht-dolt
sourcecraft.dev/bigbes/sr-ht-ecore ~bigbes/sr-ht-ecore

Client setup

Two settings, and the second one matters as much as the first: this instance runs no checksum database, so the go command has to be told not to look for one.

go env -w GOPROXY=https://go.srht.bigb.es,direct
go env -w GONOSUMDB=go.bigb.es,go.srht.bigb.es

Do not reach for GOPRIVATE here. It implies GONOPROXY, which switches this proxy off for exactly the modules it exists to serve, and a private module then fails to fetch instead of going through the one thing that can read it.

Modules live under two names. go.bigb.es/<name> says nothing about where the code is and is resolved by looking; go.srht.bigb.es/~owner/repo names its repository outright. Both are fetched through the one GOPROXY above.

Private modules

A private module needs a credential. Mint a token with the go:read grant at https://tokens.srht.bigb.es and put it in ~/.netrc:

machine go.srht.bigb.es login <you> password <token>
machine go.bigb.es login <you> password <token>