Skip to content

(Possibly) Provide OpenVSX as default Registry #1604

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.

Sign up for GitHub

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

Jump to bottom
Closed
sr229 opened this issue May 4, 2020 · 2 comments
Closed

(Possibly) Provide OpenVSX as default Registry #1604

sr229 opened this issue May 4, 2020 · 2 comments

Comments

@sr229
Copy link
Contributor

sr229 commented May 4, 2020

It seems OpenVSX is a successful implementation of the Visual Studio Code Registry, and has been used our friends from @eclipse-theia. I think it would be nice for us to move away from the private registry method and move the extension support to OpenVSX.

Another good benefit of this is that Enterprise customers can host their own registry using the same OpenVSX registry code.
@sr229
Copy link
Contributor Author

sr229 commented May 4, 2020

As an added bonus, this will also solve all of the listed extension issues we had previously here - as we can divert the requests to the plugin authors instead to support OpenVSX instead of Coder handling the burden.

@cmoog
Copy link
Contributor

cmoog commented May 4, 2020

The code-server extension marketplace currently supports over 20 times the number of extensions available in the OpenVSX registry. Please reference #1473 to track this issue.

Closing because this is a duplicate.

@cmoog cmoog closed this as completed May 4, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@cmoog @sr229