Thanks a lot, Alexis, for your response, and your proposal.
I got to know ProGet and found it one of the best solutions to my needs, but I can't afford to pay the license for a server, currently, and the only feature I really need is some sort of access control policy to the exposed package feed, which, AFAICT is the one feature missing from the free edition.
So, ProGet is more than I need, but too much for the cost, or an excellent free product missing the one feature I need.
I was hoping to get the Nuget.Server package running (this was easy) and then hack onto it some access control.
As I did a deep dive into the Nuget.Server codebase, I quickly discovered that one of my favourite projects is built on top of layers shaped in different ways, and I can't get the philosophy behind each layer, if any.
Simple questions like "v1/v2/v3, which one I need?" or "What do I need to support for a barebone feed?" I was hoping for some sort of documentation, even something like: implement what's in the "xyz" class in the nuget codebase.
I'm probably just going to sniff out the basic client/server communication and reimplement my own nuget.server version, but it's going to take a while.
Thanks!
Alberto Chiesa