Native Winget Repo Server for Windows Server

Open
#232 7 comments 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
csharp, sql
Domain
api, backend, databases

Research direction

Start by reviewing this repository's existing REST-based package source and the issue's proposed C#/.NET 8 and local SQL Server direction. No files, tests, or entry points are named, so the first step is to define the server's required scope and configuration needs. Done should mean an agreed implementation plan with clear requirements for the Windows Server service and management interface.

Written by the indexing model from the issue text.

Description

Issue-Feature
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

  1. Writing the server/service in C# using .Net 8.0 and ms sql local db for the database
  2. Implement it using built in web components for site management.
Dominant language
C#
Stars
317
Forks
79
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/winget-cli-restsource

All issues in microsoft/winget-cli-restsource

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.