Thanks for answering my question! So yes, if I intend to use go and study the packages I'd have to rely on beforehand, if they're all hosted on GitHub should make me steer away from Golang. Or at least plan to cache the packages I need locally so CI always have something to work with when building.
Alternatively, could we ourselves build an automatic mirror so there's a redundant supply provider that doesn't depend on a maintainer's choice of git forge
This should be the first thing to learn when starting with Golang.
Let's take a project I worked on for a couple of years some time ago, it has this go.mod file: <a href="https://gitlab.com/nunet/device-management-service/-/blob/main/go.mod?ref_type=heads" rel="nofollow">https://gitlab.com/nunet/device-management-service/-/blob/ma...
Is it just changing all instances of `github.com` to `proxy.golang.org`? Shouldn't `go build` warn about using third party proxies for dependencies? Should `go get` offer a flag to automatically use the proxy when adding dependencies?
gchamonlive · · focus · HN ↗
Alternatively, could we ourselves build an automatic mirror so there's a redundant supply provider that doesn't depend on a maintainer's choice of git forge
<a href="https://news.ycombinator.com/item?id=49434625">https://news.ycombinator.com/item?id=49434625
Mawr · · focus · HN ↗
gchamonlive · · focus · HN ↗
Let's take a project I worked on for a couple of years some time ago, it has this go.mod file: <a href="https://gitlab.com/nunet/device-management-service/-/blob/main/go.mod?ref_type=heads" rel="nofollow">https://gitlab.com/nunet/device-management-service/-/blob/ma...
Is it just changing all instances of `github.com` to `proxy.golang.org`? Shouldn't `go build` warn about using third party proxies for dependencies? Should `go get` offer a flag to automatically use the proxy when adding dependencies?