|
7 | 7 | - [Community Projects (awesome-code-server)](#community-projects-awesome-code-server)
|
8 | 8 | - [How can I reuse my VS Code configuration?](#how-can-i-reuse-my-vs-code-configuration)
|
9 | 9 | - [Differences compared to VS Code?](#differences-compared-to-vs-code)
|
| 10 | + - [Installing an extension](#installing-an-extension) |
10 | 11 | - [How can I request a missing extension?](#how-can-i-request-a-missing-extension)
|
| 12 | +- [Installing an extension manually](#installing-an-extension-manually) |
11 | 13 | - [How do I configure the marketplace URL?](#how-do-i-configure-the-marketplace-url)
|
12 | 14 | - [Where are extensions stored?](#where-are-extensions-stored)
|
13 | 15 | - [How is this different from VS Code Codespaces?](#how-is-this-different-from-vs-code-codespaces)
|
@@ -82,15 +84,43 @@ These are the closed source extensions presently unavailable:
|
82 | 84 |
|
83 | 85 | For more about the closed source parts of VS Code, see [vscodium/vscodium](https://github.com/VSCodium/vscodium#why-does-this-exist).
|
84 | 86 |
|
| 87 | +### Installing an extension |
| 88 | + |
| 89 | +Extensions can be installed from the marketplace using the extensions sidebar in |
| 90 | +code-server or from the command line: |
| 91 | + |
| 92 | +```shell |
| 93 | +code-server --install-extension <extension id> |
| 94 | +# example: code-server --install-extension wesbos.theme-cobalt2 |
| 95 | +``` |
| 96 | + |
85 | 97 | ## How can I request a missing extension?
|
86 | 98 |
|
87 |
| -Please open a new issue and select the `Extension request` template. |
| 99 | +We are currently in the process of transitioning to [Open VSX](https://open-vsx.org/). |
| 100 | +Once https://github.com/eclipse/openvsx/issues/249 |
| 101 | +is implemented, we can fully make this transition. Therefore, we are no longer |
| 102 | +accepting new requests for extension requests. |
| 103 | + |
| 104 | +Instead, we suggest one of the following: |
| 105 | + |
| 106 | +- [Switch to Open VSX](#how-do-i-configure-the-marketplace-url) now |
| 107 | +- Download and [install the extension manually](#installing-an-extension-manually) |
88 | 108 |
|
89 |
| -If an extension is not available or does not work, you can grab its VSIX from its Github releases or |
90 |
| -build it yourself. Then run the `Extensions: Install from VSIX` command in the Command Palette and |
91 |
| -point to the .vsix file. |
| 109 | +## Installing an extension manually |
92 | 110 |
|
93 |
| -See below for installing an extension from the cli. |
| 111 | +If an extension is not available from the marketplace or does not work, you can |
| 112 | +grab its VSIX from its GitHub releases or build it yourself. |
| 113 | + |
| 114 | +Once you have downloaded the VSIX to the remote machine you can either: |
| 115 | + |
| 116 | +- Run the `Extensions: Install from VSIX` command in the Command Palette. |
| 117 | +- Use `code-server --install-extension <path to vsix>` |
| 118 | + |
| 119 | +You can also download extensions from the command line. For instance, downloading off OpenVSX can be done like this: |
| 120 | + |
| 121 | +```shell |
| 122 | +SERVICE_URL=https://open-vsx.org/vscode/gallery ITEM_URL=https://open-vsx.org/vscode/item code-server --install-extension <extension id> |
| 123 | +``` |
94 | 124 |
|
95 | 125 | ## How do I configure the marketplace URL?
|
96 | 126 |
|
|
0 commit comments