Private NuGet server
-
Thanks, I looked at Nuget.Server but it is not what we want as it needs ASP.NET / IIS (my boss is allergic for that). I think I found a nice self-hosted alternative: ProGet https://www.slant.co/topics/16129/viewpoints/1/~private-nuget-servers~proget[^]
RickZeeland wrote:
as it needs ASP.NET / IIS (my boss is allergic for that)
You did not mentioned that in your question :) and I think that Nuget.Server is easiest solution there. Anyway I am glad that you found what you were looking for. Cheers.
No more Mister Nice Guy... >: |
-
RickZeeland wrote:
as it needs ASP.NET / IIS (my boss is allergic for that)
You did not mentioned that in your question :) and I think that Nuget.Server is easiest solution there. Anyway I am glad that you found what you were looking for. Cheers.
No more Mister Nice Guy... >: |
True, thanks for the input anyway :)
-
True, thanks for the input anyway :)
I just noticed you can actually purchase NuGet Server[^] for $9 which is a wrapper on the Nuget.Server package and allows you to run it as a Windows service without IIS (it has its own web server)
-
I just noticed you can actually purchase NuGet Server[^] for $9 which is a wrapper on the Nuget.Server package and allows you to run it as a Windows service without IIS (it has its own web server)
Nah, we can get ProGet for free ;P
-
Nah, we can get ProGet for free ;P
I've been using ProGet for just over a year and I would absolutely recommend. It took away all of the (many, many) headaches we suffered under NuGet.Server. - Installation/upgrade is a breeze with the installation wizard. Automatically installs/configures SQL server and all dependencies - Option to run on its own integrated webserver instead of IIS - Support for many types of packages in addition to NuGet - we've had great success using the extensible UPack format for client application deployment - Simplified support for NuGet symbols - just push the *.symbols.nupkg to ProGet and it sorts everything out. No need to push the regular nupkg file to one place and the symbols file to another place.
-
I'm thinking of setting up a private NuGet server for our development department. TeamCity 2017.1 seems to have NuGet support, but the documentation is confusing, it gives the impression that this is only for self built NuGet packages which are stored with the build artifacts. Anyone has got any experience with this, can I use it for standard NuGet packages ?
We use ProGet ProGet Pricing & Licensing | Inedo[^]
I'm not a player, I just code a lot! Alex Dresko
-
Nah, we can get ProGet for free ;P
We use Proget as well - as long as we still don't have Tfs /Azure DevOps. So far So happy with it. Once the symbols didn't work anymore after changing to .net core project files, but they fixed that soon enough. And user authentication might be a bit too simple in the free version. There's no restraining who may push packets and who may only have a look. Well, for being free it's great enough ;-)
-
I'm thinking of setting up a private NuGet server for our development department. TeamCity 2017.1 seems to have NuGet support, but the documentation is confusing, it gives the impression that this is only for self built NuGet packages which are stored with the build artifacts. Anyone has got any experience with this, can I use it for standard NuGet packages ?
We use Sonatype Nexus for this.
-
We use Sonatype Nexus for this.
Thanks, added it to the list here: https://www.slant.co/improve/topics/16129/~private-nuget-servers[^] :-\
-
I'm thinking of setting up a private NuGet server for our development department. TeamCity 2017.1 seems to have NuGet support, but the documentation is confusing, it gives the impression that this is only for self built NuGet packages which are stored with the build artifacts. Anyone has got any experience with this, can I use it for standard NuGet packages ?
We are doing it at my place of employment and it works well. Download source here: GitHub - NuGet/NuGet.Server: The home of the NuGet.server package, a lightweight standalone NuGet server[^] Load it up on VS and deploy to a web server near you. You will need to update the web.config settings and maybe some director permissions.
Eric