-
-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
This project has been killed by ms? #27
Comments
looks like there's a workaround here: microsoft/vscode#135856 (comment) will need to update the |
I have yet to take a look at this: https://github.com/gitpod-io/openvscode-server Came up with a working script: #!/bin/sh
#Requires jq
LATEST="$(curl -fsSL https://update.code.visualstudio.com/api/commits/stable/server-linux-x64-web | jq -r 'first')"
wget https://az764295.vo.msecnd.net/stable/${LATEST}/vscode-server-linux-x64-web.tar.gz -O /tmp/vscode-server-linux-${LATEST}-x64-web.tar.gz
sudo mkdir -p /opt/vscode/${LATEST}
sudo tar --strip-components=1 -xf /tmp/vscode-server-linux-${LATEST}-x64-web.tar.gz -C /opt/vscode/${LATEST}
CODEVER="$(cat /opt/vscode/${LATEST}/package.json | jq -r '.version')"
sudo ln -sfn ${LATEST} /opt/vscode/${CODEVER}
sudo ln -sfn ${CODEVER} /opt/vscode/latest The question is wether this host (az764295.vo.msecnd.net/) will keep working... I wonder what is coming from ms... BTW, using this script in a "REMOTE HOST", it is possible to use both SSH and WEB with synchronized config and extensions.
|
seems they finally resolved this last week: microsoft/vscode#168492 (comment) I'll make the necessary updates today |
Hello, did you make necessery updates? I don't see any update for vs code docker container? |
Hello, would be interested in this as well. I needed to reset my Unraid server and the installed docker container still has this issue. |
fixed in v2.0.0 |
Now the downloaded code-server file is an html file pointing here: https://code.visualstudio.com/docs/remote/tunnels
I believe this kind of usage has just become dead? 😭
The text was updated successfully, but these errors were encountered: