Open Jose-Matsuda opened 5 hours ago
Back when I was last testing, I would use code-marketplace add
for this. So:
export ARTIFACTORY_TOKEN="my-token"
./code-marketplace add --artifactory http://artifactory.server/artifactory --repo extensions [extension to add]
Or, if you want to take the existing extensions you had in the image, you can just copy them exactly as they are into the Artifactory repo.
Back when I was last testing, I would use
code-marketplace add
for this. So:export ARTIFACTORY_TOKEN="my-token" ./code-marketplace add --artifactory http://artifactory.server/artifactory --repo extensions [extension to add]
Or, if you want to take the existing extensions you had in the image, you can just copy them exactly as they are into the Artifactory repo.
Would that just be putting the .vsix files at any level in say a generic local repository?
I don't think there's documentation for this but for reference I'm in a locked-down k8s cluster serving jupyter notebooks with code-server pointing to a running code-marketplace pod for extensions. Just so users could install extensions asap, we baked in some default extensions into the built
code-marketplace
image but are now looking to not have to do that. We do have Jfrog Artifactory running and pushing extensions to a local artifactory repo would be much easier.I know @janLo was able to do this, if you could share what you did with your artifactory that would be amazing :)