On Wed, Dec 12, 2018 at 10:15 PM snmed <sandro.p.da...@gmail.com> wrote:
> Thank you very much for your reply. It seems to be a possible way to do > it, what do you think about the athens way? In my point of view it would be > the easiest way as far i can preload the athens cache with all the required > packages, > And then the only thing a developer has to do, is to set the GOPROXY to > the athens instance. > > Such setups are supported by the Go from its onset. >> >> 1. DMZ box where `go get` can reach external repositories >> 2. IDP internal distribution point - with vetted go tools and vetted libs >> > The methods in athens seem to be a good starting point. The challenge is the vetting when a big resource like this has a lot of changes often quickly. Be sure to anchor yourself in a strategy that can scale. I can see success spawning multiple projects that cannot see each other multiplying permutations. A DMZ box is not an air gap but might be necessary as a first step in protect the transfer and stage the process before anything crosses the air gap. It sounds like a project ... it does sound as if you understand the challenges. You will depend on Athens so that needs to be tracked as well. Sounds like fun. -- T o m M i t c h e l l -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
