this post was submitted on 03 Aug 2023
2 points (100.0% liked)

.NET

1502 readers
1 users here now

Getting started

Useful resources

IDEs and code editors

Tools

Rules

Related communities

Wikipedia pages

founded 2 years ago
MODERATORS
erlingur
starman
Spyros
2
Private Nuget feed hosting (self.dotnet)
submitted 1 year ago by canpolat to c/dotnet
12 comments fedilink hide all child comments
 

I wanted to exchange some experience regarding private NuGet feed hosting solutions.

We have used MyGet for years both for our private and public packages. But recently it became so unstable that it would not be responsible to not investigate the alternatives. I looked into Azure Artifacts first because, we already have Azure Devops and it comes free. The transition was mostly painless (I plan to write about it in more detail soon). But hosting public feeds doesn't seem as easy. One needs to create a public project just for that. So, we still use MyGet for public feeds for now. But will move them also elsewhere.

What are your experiences with private feed hosting? Do you host them yourselves or use a paid service?

you are viewing a single comment's thread
view the rest of the comments
[–] atheken 3 points 1 year ago* (last edited 1 year ago) (1 children)

At my last job, we used sleet in combination with S3 and a cloudfront distribution with an authorization lambda for pulling packages. I think the whole setup took about 2 hours and it was rock solid.

This was necessary because we were using Octopus Deploy and were bumping into storage limits with their built in feed.

We were a relatively small team, and relatively slow package publish rate (10x a day, probably).

Biggest issue with sleet is that it’s not going to support “pull through” so you’ll need to have multiple nuget feeds configured.

[–] nibblebit 1 points 1 year ago (1 children)

ooh i haven't heard of sleet that looks so neat.

10 publishes a day? Is that slow? I'm at a 20 man team and we run up to about 10 a month. is your final product a suite of packages or are you like only using package references in your projects?

[–] atheken 2 points 1 year ago

We had about 10-15 lambda “Microservices” each of these packaged up a service/contracts library to be consumed by other services that used them. We also had an MVC API and a few windows services that were built for a “distributed monolith”.

We built all all branches on every push, we tried to deploy updates multiple times a week.

We had 4 devs working on .net

The main thing with sleet is that I made zero effort to prune anything from the feed, so eventually it might cost a few dollars per month for S3 storage, but it was literally zero maintenance after we got it set up.