-
Notifications
You must be signed in to change notification settings - Fork 24
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
Allow to fallback to VS Code marketplace for missing packages #52
Comments
I do not think we can specifically point to the VS Code marketplace for legal reasons. But, it would be cool to implement a generic fallback so you can specify a different marketplace, like say Open VSX. |
Although I wonder if some kind of caching proxy is a better fit for this use case. |
What I want is to have a single URL that I can configure for people to have both private and public packages For me it's enough to just proxy it Yes, a generic "fallback url" is a good config, so it's users who bear legal responsibility |
@code-asher Maybe some functionality like Nexus repository manager/Docker registry that can act as a proxy of an upstream extension registry (i.e., open-vsx.org). In this way, install extension that requires specific versions will not fail if that version is missing in local marketplace. updated: I find that ovsx have implemented the proxy mode (also mirror mode). So, code-marketplace should main serve as an offline service, on which extension can only be added via files. |
I also just learned about https://github.com/LOLINTERNETZ/vscodeoffline Not an endorsement, I have never used it, but maybe it is worth looking at. |
With a lot of package management feeds, it's common to support falling back to upstream feed for missing packages, so you can do all operations with a single feed url.
Service should return local packages if it's available, and fall back to real marketplace if it's not.
The text was updated successfully, but these errors were encountered: