We stood up an internal nuget feed on our intranet using Nuget.Server 1.5. It's available externally using https://nuget.ourdomain.com using host header redirection on IIS7/Win2008. To add it in VS as a package source requires using the https://nuget.ourdomain.com/nuget.
I can manually put .nupkg files in /Packages they show up. All's fine and dandy. Except for the command line. These command lines work for nuget.exe against our feed:
- nuget list ourapikey -source https://nuget.ourdomain.com/nuget
- nuget push Foo.pkg ourapikey -source https://nuget.ourdomain.com
- nuget delete Foo 1.0 ourapikey -source https://nuget.ourdomain.com
Why does list require the trailing /nuget? Is this intentional? Web.config also has the app setting for packages path set to a directory with full permissions for all authenticated users. I would like to just use the same
value for -source. (push and delete fail with the trailing /nuget.) I'm trying to sell using this going internally and it's a hard sell when there's edges like this. Help?