Introduce dependency proxy as an instance setting for caching OpenVSX extensions
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13.8k
- Forks
- 1.4k
- Avg merge
- 17h 58m
- Merged PRs (30d)
- 5
Description
Problem to solve
From the relevant RFC: OpenVSX self-hosting POC (internal):
We would like to prototype self hosting of OpenVSX to improve reliability on SaaS and self-hosting customers.
See also relevant discussions[1][2] (internal).
Proposal
Introduce dependency proxy as an instance setting for caching OpenVSX extensions.
Here's an early design on how this could look like:
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or implementation entry points; begin by reviewing the linked OpenVSX self-hosting RFC and the two referenced discussions. Clarify the instance-setting design and caching scope before identifying the affected configuration, proxy, and extension-related code. Done means the dependency proxy can be configured as an instance setting and caches OpenVSX extensions as specified.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100