Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.
If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!
Internal ProGet server: does connecting to external feeds offer any benefits?
-
Hi all,
Was wondering about this one. I'll have two ProGet servers: one for the internal project staff to use, while the other will be on the outside for the public to use and benefit from (anonymous authentication). The internal one; most of us are Chocolatey users, so in light of Otter also being on the scene to help configure new servers, I'm assuming that it might be beneficial to add a connector to the Chocolatey Repository both for workstations to use (configure Choco to point initially to our ProGet server), and then on the server side in combination with Otter? (Otter flips to ProGet, flips to Choco). Is this more complex of a configuration than we need? Does it seem like I'm trying to use a ProGet feature just because it's there? If so, are any alternative configurations suggested by the community? Thanks.Product: ProGet
Version: 5.0.10
-
Once you have an internal ProGet server set-up, there's little benefit in having your internal, package-consuming clients (Chocolatey, but also NuGet, npm, and so on), pointing directly to the corresponding public package galleries.
Even if the request is only forwarded for now, you get the benefit of caching (in case the public gallery goes down). Also, you can "mix in" your own private packages, without needing to use a different feed.
But most importantly, you can restrict the public feed later. For example, you may only put "approved" packages there, and for Chocolately especially, you may "internalize" the package, which means the contents of the package will be inside the package zip file, instead of downloaded from an external web resource.
-
That's actually pretty awesome. that's exactly what I was sort of thinking of doing.