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!
Implications of Pull To ProGet
-
What are implications of using the "Pull To ProGet" feature? I understand that using the cache will download copies of the package, to improve performance and in case nuget.org or bower's or NPM's registries go down, right? We used to use the nuget mirror command when we were using a NuGet Gallery.
If I pull a package to ProGet, should I now see 2 packages? One for the connector's instance and one for the pulled instance?
What happens if I pull a package to ProGet, then that package deploys a new version to NuGet, for example? Do I need to repull it? Will I be able to see the new version in the pulled package?
Can unpull a package? What happens in that case?
Thanks!
Product: ProGet
Version: 3.7.3 -
With remote connector caching enabled (default is enabled), there is almost no reason to pull a package to your feed.
The reason the Pull feature is there, for example, is so you can pull down your "approved" packages, then remove the connector which in turn makes that package part of your local feed.
Anyway, pulled packages are keyed by ID and version, so if a new version were released, you'd have to pull that. Check out some of the features we have planned on the Road Map which will better handle scenarios for users who pull packages often.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login