afrikda.blogg.se

This might be great for personal use, but it becomes tricky in CI, especially if we are restoring packages inside a Docker container.

Reading packages from the NuGet repository does not use the API Key but your regular credentials. To enable it, simply go to Security -> Realms and add the NuGet API Key Security Realm to the list of Active realms. why do you get a NuGet repository out of the box, but it’s effectively read-only?). This is mentioned in the documentation but it’s not intuitive (i.e. The API key belongs to a user, so it is available under Account -> NuGet API Key -> Access API Key.Īn important thing is that the key won’t work if you don’t activate the NuGet API Key Security Realm. The repository’s feed is available at In order to publish to this NuGet repository, we need to get an API Key. Out of the box, Nexus has a ready to use NuGet repository, so I don’t have to configure anything there. On a side note, the UX/UI of Nexus has improved since version 2, but it’s still a bit old fashioned in my personal opinion.

All I had to do was copy the example from the documentation with no changes at all (since my username is already nexus and my installation directory is effectively /opt/nexus).Īt this point, it is possible to access the UI at port 8081 (assuming no firewall is blocking it) and login to Nexus with the default admin credentials which are admin and admin123. The next step is to install Nexus as a systemd service.