BaGet | A lightweight NuGet and symbol server | DevOps library

In our development environment, we have set up a NuGet local server (BaGet). We have adopted the Gitflow idea. When a library is ready to be released on Baget, the developer should first increase the Tag on the master branch (which needs to be approved first via a pull-request), then push the library to the Baget. We do this to keep the version of Git and Nuget in sync.

The process of keeping versions in sync (Git tag & NuGet version) is controlled manually by the developer and sometimes some team members forget to define the Git version tag and just push the library to Baget.

It would be a great help if the script could check the Current Git Tag before pushing the library to the Baget server, and only push it if the Tag and Version are the same. This can prevent pushing a version without matching Tag on git.

We use this script for pushing to Baget:

I'm trying to setup BaGet in Docker with Docker Compose behind an Apache2 reverse proxy, where Apache2 is also running in Docker from Docker Compose.

I've done this successful with Jenkins and Sonar, but with BaGet (http://localhost:8000/baget) I get "Service Unavailable" even though it's available directly on its own port, e.g.: http://localhost:5555/.

My Docker Compose file looks like this:

I developed a library, which is published on BaGet and used in one of my projects. When extending models in the library, I publish it to BaGet and then update the package in the referencing project using VS NuGet package manager. Somestimes, VS doesn't recognize those changes in Intellisense.

Example: I added a model field AuthorUserName in the library project and publish it: