Full Offline / closed network capabilities including feed generation
FabianNiesen opened this issue · 5 comments
Description of the new feature / enhancement
I have read through various feature requests and documents, but have not yet found a suitable solution.
The problem
We have customers with encapsulated networks, which means data transfer only via secure storage exchange (Mowing Data with Usb thump drives between the networks). We can adapt the manifests so that the data sources are offline, no problem. But we need a feed, and we need to create it within the environment. Directly specifying the manifest for each file, as suggested in microsoft/winget-cli#226, is not an option.
The other previous solution like microsoft/winget-cli#203 microsoft/winget-cli#213 or the article https://github.com/microsoft/winget-cli-restsource is not an option (Due Azure requirements).
Proposed technical implementation details
My wish / proposed solution would be a meta-manifest as a feed in which all manifests can be added. This could then simply be stored on any web server via https and automatically updated with a PowerShell script.
@FabianNiesen - for personal curiosity - could you provide a little more detail on what you are looking for? I see @denelon marked this as a duplicate - and I largely agree with that - but if I read your statement correctly, I think you may be asking for more in addition to #158.
To me, it sounds like your asking for a way to upload multiple manifests at once - not just one at at time? Did I read that correctly?
I've started work on WinGetty over here: https://github.com/thilojaeggi/WinGetty which technically works without any Internet access. (Only need to install the root CA when self signing, duh)
Most features work already and I'm working on adding silent installers that can be configured directly in the Webinterface instead of having to pass them in the winget install command.
@thilojaeggi, the project doesn't have a license. Are you leaning towards a commercial solution or an OSS solution?
Totally forgot to add one, just added one. It's an OSS solution.