Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit c07740a

Browse files
Akash SatheesanGirlBossRush
Akash Satheesan
authored andcommitted
docs: update FAQ with extension gallery info (#2672)
1 parent 1b60ef4 commit c07740a

File tree

1 file changed

+12
-17
lines changed

1 file changed

+12
-17
lines changed

‎docs/FAQ.md‎

Lines changed: 12 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -101,8 +101,11 @@ Service](https://cdn.vsassets.io/v/M146_20190123.39/_content/Microsoft-Visual-St
101101
> Visual Studio Products and Services.
102102

103103
Because of this, we can't offer any extensions on Microsoft's marketplace.
104-
Instead, we've created a marketplace offering open-source extensions. The
105-
marketplace works by scraping GitHub for VS Code extensions and building them.
104+
Instead, we use the [Open-VSX extension gallery](https://open-vsx.org), which is also used by various other forks.
105+
It isn't perfect, but its getting better by the day with more and more extensions.
106+
107+
We also offer our own marketplace for open source extensions, but plan to
108+
deprecate it at a future date and completely migrate to Open-VSX.
106109

107110
These are the closed-source extensions that are presently unavailable:
108111

@@ -118,15 +121,8 @@ For more about the closed source portions of VS Code, see [vscodium/vscodium](ht
118121

119122
## How can I request an extension that's missing from the marketplace?
120123

121-
We are in the process of transitioning to [Open VSX](https://open-vsx.org/).
122-
Once we've [implemented Open
123-
VSX](https://github.com/eclipse/openvsx/issues/249), we can finalize this
124-
transition. As such, we are not currently accepting new extension requests.
125-
126-
In the meantime, we suggest:
127-
128-
- [Switching to Open VSX](#how-do-i-configure-the-marketplace-url) now
129-
- Downloading and [installing the extension manually](#installing-an-extension-manually)
124+
To add an extension to Open-VSX, please see [open-vsx/publish-extensions](https://github.com/open-vsx/publish-extensions).
125+
We no longer plan to add new extensions to our legacy extension gallery.
130126

131127
## How do I install an extension?
132128

@@ -159,20 +155,19 @@ You can also download extensions using the command line. For instance,
159155
downloading from OpenVSX can be done like this:
160156

161157
```shell
162-
SERVICE_URL=https://open-vsx.org/vscode/gallery ITEM_URL=https://open-vsx.org/vscode/item code-server --install-extension <extension id>
158+
code-server --install-extension <extension id>
163159
```
164160

165161
## How do I use my own extensions marketplace?
166162

167163
If you own a marketplace that implements the VS Code Extension Gallery API, you
168-
can point code-server to it by setting `$SERVICE_URL` and `$ITEM_URL`. These correspond directly
169-
to `serviceUrl` and `itemUrl` in VS Code's `product.json`.
164+
can point code-server to it by setting `$EXTENSIONS_GALLERY`.
165+
This corresponds directly with the `extensionsGallery` entry in in VS Code's `product.json`.
170166

171-
For example, to use [open-vsx.org](https://open-vsx.org), run:
167+
For example, to use the legacy Coder extensions marketplace:
172168

173169
```bash
174-
export SERVICE_URL=https://open-vsx.org/vscode/gallery
175-
export ITEM_URL=https://open-vsx.org/vscode/item
170+
export EXTENSIONS_GALLERY='{"serviceUrl": "https://extensions.coder.com/api"}'
176171
```
177172

178173
Though you can technically use Microsoft's marketplace in this manner, we

0 commit comments

Comments
(0)

AltStyle によって変換されたページ (->オリジナル) /