Using GitHub to host a NuGet feed/packages?

I want to setup CD for my repos, but I have a few problems.

1. I’d like to deploy every commit to a NuGet feed.
2. I don’t want to spam nuget.org with each and every commit (even pull requests).
3. My packages contain native libraries which eat a lot of space. This rules out MyGet since there storage quotas are low.

This leads me to my next question.

What about creating a GitHub repository that contains the required files for a valid NuGet feed?

“But what about the large nupkg files?” Yeah, you wouldn’t want to commit large binaries into a repository. So instead, I will configure my CI/CD to auto-upload my nupk files to a GitHub release which has no size limits. The static files the represent my NuGet feed will point to the nupkg files uploaded to the GitHub release.

I’d like to do something like this.

# Assume v0.1.0 is a GitHub release in the repo "pauldotknopf/myfeed".
sleet push pauldotknopf/myfeed:v0.1.0 --source myGitRepoFeed

The GitHub release would be inspected and would update the NuGet feed.

What do you think? Is this feasible? If so, would you be open to a PR?

[emgarten]

If anyone has instructions for getting sleet to work with github I’m happy to take a doc PR for it https://github.com/emgarten/Sleet/tree/master/doc

[inosik]

I’m experimenting with a simpler version of this at the moment. This is what my sleet.config looks like:

{
  "sources": [
    {
      "name": "gitlab",
      "type": "local",
      "path": "$rootDir$/v3",
      "baseURI": "https://gitlab.my-company.local/my-team/packages/raw/master/v3"
    }
  ]
}

The feed URL for clients is https://gitlab.my-company.local/my-team/packages/raw/master/v3/index.json.

I’m building a small web service based on Giraffe which implements the NuGet push endpoint and commits the pushed package file via GitLabs API to the repository. What I have left to do is to set up a CI job in GitLab to update the feed when a package file is commited.

I’m sure this can also be done with GitHub. Probably the feed can also be served with GitHub Pages.

“But what about the large nupkg files?” Yeah, you wouldn’t want to commit large binaries into a repository.

Is this a problem? Maybe Git LFS can be used to reduce the repository size.