|
10 | 10 | - [How can I reuse my VS Code configuration?](#how-can-i-reuse-my-vs-code-configuration)
|
11 | 11 | - [Differences compared to VS Code?](#differences-compared-to-vs-code)
|
12 | 12 | - [How can I request a missing extension?](#how-can-i-request-a-missing-extension)
|
| 13 | + - [Installing VSIX Extensions via the Command Line](#installing-vsix-extensions-via-the-command-line) |
13 | 14 | - [How do I configure the marketplace URL?](#how-do-i-configure-the-marketplace-url)
|
14 | 15 | - [Where are extensions stored?](#where-are-extensions-stored)
|
15 |
| - - [Installing VSIX Extensions via the Command Line](#installing-vsix-extensions-via-the-command-line) |
16 | 16 | - [How is this different from VS Code Codespaces?](#how-is-this-different-from-vs-code-codespaces)
|
17 | 17 | - [How should I expose code-server to the internet?](#how-should-i-expose-code-server-to-the-internet)
|
18 | 18 | - [Can I store my password hashed?](#can-i-store-my-password-hashed)
|
@@ -89,11 +89,24 @@ For more about the closed source parts of VS Code, see [vscodium/vscodium](https
|
89 | 89 |
|
90 | 90 | Please open a new issue and select the `Extension request` template.
|
91 | 91 |
|
92 |
| -If an extension is not available or does not work, you can grab its VSIX from its Github releases or |
| 92 | +If an extension is not available or does not work, you can grab its VSIX from its GitHub releases or |
93 | 93 | build it yourself. Then run the `Extensions: Install from VSIX` command in the Command Palette and
|
94 | 94 | point to the .vsix file.
|
95 | 95 |
|
96 |
| -See below for installing an extension from the cli. |
| 96 | +### Installing VSIX Extensions via the Command Line |
| 97 | + |
| 98 | +If you're using code-server on a remote machine, it might be easier to install extensions via the command line. Follow these steps: |
| 99 | + |
| 100 | +1. [optional] create a directory to store your extensions: `mkdir plugins` |
| 101 | +2. Find the extension you want i.e. `https://open-vsx.org/extension/stylelint/vscode-stylelint` and grab the name and identifier: `stylelint/vscode-stylelint` |
| 102 | +3. Download extension to directory: |
| 103 | + ```sh |
| 104 | + curl 'https://open-vsx.org/api/stylelint/vscode-stylelint' | jq '.files.download' | xargs curl --compressed -L -o plugins/stylelint.vsix |
| 105 | + ``` |
| 106 | +4. Install in code-server |
| 107 | + ```sh |
| 108 | + code-server --install-extension stylelint.vsix |
| 109 | + ``` |
97 | 110 |
|
98 | 111 | ## How do I configure the marketplace URL?
|
99 | 112 |
|
@@ -135,21 +148,6 @@ code-server --install-extension ms-python.python
|
135 | 148 | code-server --install-extension downloaded-ms-python.python.vsix
|
136 | 149 | ```
|
137 | 150 |
|
138 |
| -### Installing VSIX Extensions via the Command Line |
139 |
| - |
140 |
| -If you're using code-server on a remote machine, it might be easier to install extensions via the command line. Follow these steps: |
141 |
| - |
142 |
| -1. [optional] create a directory to store your extensions: `mkdir plugins` |
143 |
| -2. Find the extension you want i.e. `https://open-vsx.org/extension/stylelint/vscode-stylelint` and grab the name and identifier: `stylelint/vscode-stylelint` |
144 |
| -3. Download extension to directory: |
145 |
| - ```sh |
146 |
| - curl 'https://open-vsx.org/api/stylelint/vscode-stylelint' | jq '.files.download' | xargs curl --compressed -L -o plugins/stylelint.vsix |
147 |
| - ``` |
148 |
| -4. Install in code-server |
149 |
| - ```sh |
150 |
| - code-server --install-extension stylelint.vsix |
151 |
| - ``` |
152 |
| - |
153 | 151 | ## How is this different from VS Code Codespaces?
|
154 | 152 |
|
155 | 153 | VS Code Codespaces is a closed source and paid service by Microsoft. It also allows you to access
|
|
0 commit comments