Hi all,
I'm currently setting up a new ProGet instance, migrating from a relative large instance with a few "catch all" feeds, to a new install with a more granular set of feeds. Ideally, I'd like to implement consistent set of URL patterns, including possible forms of 'namespacing' for multiple tenants, and clear separation between repository types (including in paths). We use CI/CD heavily to validate e.g., registry usage; so being able to create some consistent patterns would be great.
Based on the current options and documentation, I understand that the following patterns apply (by default);
- single "URL segment" feed name, no urlencodable characters (i.e., no
/ allowed)
- always prefixed with a feed type, though depends on the feed type, e.g.;
nuget for NuGet, PowerShell, Chocolatey
helm, npm, etc. for their respective package managers
- Docker has no path prefix
- alternate names can be defined, but have the same restrictions
This can lead to somewhat restrictive and sometimes confusing feed URLs (e.g., the debian prefix being used for general apt-compatible systems, the Docker feeds having no prefix at all).
I'm therefore wondering if there are alternative strategies to allow more flexible feed naming? Possibly via internal configuration or otherwise?
One option I'm considering is layer a proxy in front of ProGet, to provide the URL rewriting to map to ProGet-compatible names. e.g.,;
proget.org.com/ps/tenant-a to proget.org.com/nuget/ps-tenant-a
or
proget.org.com/docker/tenant-a to proget.org.com/docker-tenant-a
I would love to head your thoughts.
Best,
Cyril