-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Native Winget Repo Server for Windows Server #232
Comments
to understand better where this idea is coming from. See that it could be difficult to implement with dependencies for Windows Server team and winget, and limitation of an LTSC release, but well the base idea is good. maybe we can instead of "inbox" bringing up something like that was done with Azure Arc post-release. |
"ms sql local db" we might use the Windows Server internal role "Windows Internal Database". But technically would have doubts. It was intended for once smaller WSUS and IPAM. Over the years this WID proves giving admins hard nuts to troubleshoot, maintenance (before ajtek WAM) since this is a very special version of SQL LocalDB. On top of that this one is still using SQL 2012 or such, would need to revisit this information on WS 2025. |
This is one of two issues that prevents us from using winget. Our scenario is simple. A couple of thousand servers and no internet connection. About the database. For smaller use cases i would prefer just a single textfile (after all - that is how it always has been done in the Linux world) |
@matsmcp you can run https://github.com/omaha-consulting/winget.pro offline. It's an alternative implementation of a private winget repo. (I am one of the authors.) |
Can recommend winget.pro (online version) after an evaluation. Very powerful. |
@mherrmann looking at it :) |
Is there any advancement on this one ? |
Description of the new feature / enhancement
Currently, there is no good solution to host an on-prem winget repo that does not connect back to Azure.
The idea would be to create a Winget Repo Server/Service for Windows Server that could easily configured by the managing end-user.
Proposed technical implementation details
This could be done by
The text was updated successfully, but these errors were encountered: