Sleet
Sleet copied to clipboard
emgarten
Custom index.html
Maybe an index.html could be generated at the root of the container, and then using the new static website feature of Azure this would be served on the main url. That could include a static page to list the packages and the versions using some SPA application. This file could also be hosted somewhere else, and be compatible with any v3 feed I assume.
This would be a great feature!
index.html could be added at init/recreate time when the feed is first set up. It could read the package index json file to find all ids/versions.
I don't have a lot of recent front end experience myself so I'm going to mark this as up for grabs. I'm happy to help review any changes for this or discuss ideas.
In my opinion.
If you want to descory the feed , maybe Nuget explorer is quite enough. https://www.microsoft.com/en-us/p/nuget-package-explorer/9wzdncrdmdm3?activetab=pivot:overviewtab#
If you want to share some key infomation about the feed. It should not belong to this tool.
BaGet's UI is a React app that should work against any NuGet V3 API. I've deployed this UI as a static website on Azure Blob Storage before. I think there's potential here to modularize the UI so that other projects like Sleet can use it. We'd need to:
- Decouple the UI from BaGet
- Remove BaGet branding
- The documentation link should point to Sleet's documentation
- There's a few BaGet specific additions to the V3 API, like download counts and readmes. This would need to be removed for Sleet
- Support client-side searching on Sleet search results
I'm not a frontend expert either so I'd be open to suggestions on the best architecture to allow Sleet and BaGet to reuse the same frontend components.
A common v3 feed static UI would be great.
Client side searching would probably be the biggest change for Sleet since it doesn't have search, and to drive that it might need to read the package index, which is also unique to sleet to discover all package ids.