@@ -166,26 +166,8 @@ platform images are hosted in Coder's Docker Hub repo.
166
166
## Extensions marketplace
167
167
168
168
Coder users in an air-gapped environment cannot access the public VS Code
169
- marketplace. However, you can point Coder to an air-gapped instance of
170
- [ Open VSX] ( https://github.com/eclipse/openvsx ) to serve assets to users. For
171
- instructions on how to do this, see
169
+ marketplace. However, you can point Coder to an air-gapped instance of either
170
+ [ Coder's code-marketplace OSS] ( https://github.com/coder/code-marketplace ) or
171
+ [ Open VSX] ( https://github.com/eclipse/openvsx ) to serve VS Code extensions to
172
+ users. For instructions on how to do either approach, see
172
173
[ Extensions] ( ../../admin/workspace-management/extensions.md ) .
173
-
174
- Please review the [ Open VSX deployment wiki] for more information on setting up
175
- your Open VSX deployment. Note that there are several components involved,
176
- including:
177
-
178
- - The server application, available as the
179
- [ openvsx-server Docker image] ( https://github.com/eclipse/openvsx/pkgs/container/openvsx-server )
180
- - A PostgreSQL instance to hold the metadata of the published extensions
181
- - If you use just a database for storage, Open VSX stores everything as binary
182
- data, which can increase the storage and network throughput of the database
183
- considerable. As such, Open VSX recommends leveraging external storage
184
- (e.g., Azure Blob Storage or Google Cloud Storage)
185
- - Elasticsearch, which Open VSX uses as the default search engine for search
186
- queries that originate from the web UI; this is optional, since you can either
187
- turn off searches or use database queries
188
- - GitHub OAuth for user authentication
189
-
190
- [ open vsx deployment wiki] :
191
- https://github.com/eclipse/openvsx/wiki/Deploying-Open-VSX
0 commit comments