I have a build server that pulls nuget packages on every build, and currently have a NugetGallery deployed internally for custom packages. Right now that eats bandwidth like no tomorrow (not a huge deal, but I want to be kind and make things faster for us).
So I want to auto-mirror repos and cache them.
So far I have a few options: MyGet, which is a cloud-only offering (so no), and Proget (which I'm leaning towards). Are there any other options for auto-mirroring I'm missing?
NuGet 3.5 and earlier uses packages-cache instead of the http-cache, which is located in %localappdata%\NuGet\Cache . By using the cache and global-packages folders, NuGet generally avoids downloading packages that already exist on the computer, improving the performance of install, update, and restore operations.
The API key acts as an alias for the user account, so the same API key is used for all NuGet repositories within the repository manager.
Figure 1: NuGet Packages are installed in the packages folder located in a solution's root directory.
Open Visual Studio, go to Tools -> NuGet Package Manager -> Package Manager Settings menu. Click Clear All NuGet Cache(s) button in options dialog then clearing process is started. Once NuGet cache location is cleared, click ok button.
Klondike is an open-source NuGet package manager that you can deploy privately to your own servers.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With