gitpod-io
Answered and Added some FAQ in Readme section
FAQ'S
- How is OpenVSCode Server different from VS Code?
- It makes use of the power of the cloud - dependencies, compilation, testing, large data sets can all be run on machines far more powerful than your laptop.
- How is OpenVSCode Server different from Gitpod?
-
If you want one-click, fully automated developer environments that give yourself and your team an unparalleled productivity boost try Gitpod.
-
If you have a machine somewhere which you would like to access with VS Code through a browser, then go for OpenVsCode Server.
- How is OpenVSCode Server different from the Remote SSH VS Code extension?
- In OpenVSCode Server you can access those machines from any device such as iPads and Chromebooks via a web browser with the familiar VS Code experience.
- How is OpenVSCode Server different from code-server?
- Developers can simply run a Docker command to install the project on their local desktop machine and then work remotely from a much lower-powered device, such as an iPad or Chromebook. Moreover, they can install OpenVSCode Server to the cloud, and the project includes guides for running on AWS and Google Cloud, for the data science use case.
- How do I create a Node / Java / C / etc environment?
- The same way like you used to do it locally. Just run docker command
docker run -it --init -p 3000:3000 -v "$(pwd):/home/workspace:cached" gitpod/openvscode-server, visit the localhost where your vs code is up and running, and just get started with it.
Description- This is some FAQ that should be added to README.md
This PR fixes # https://github.com/gitpod-io/openvscode-server/issues/123
- How do I create a Node / Java / C / etc environment? The same way like you used to do it locally. Just run docker command docker run -it --init -p 3000:3000 -v "$(pwd):/home/workspace:cached" gitpod/openvscode-server , visit the localhost where your vs code is up and running, and just get started with it.
That answer may need more clarification, as just installing the relevant packages via the VS Code terminal has its own caveats (e.g redundant downloads on the file system). It also assumes an Ubuntu base.
- How do I create a Node / Java / C / etc environment? The same way like you used to do it locally. Just run docker command docker run -it --init -p 3000:3000 -v "$(pwd):/home/workspace:cached" gitpod/openvscode-server , visit the localhost where your vs code is up and running, and just get started with it.
That answer may need more clarification, as just installing the relevant packages via the VS Code terminal has its own caveats (e.g redundant downloads on the file system). It also assumes an Ubuntu base.
Okay, I will do research at my end with respect to it. It will be helpfull if you add your point of view in descriptive manner.
I'm curious about trying OpenVSCode (currently using code-server). Maybe I'm missing something, but #4 describes essentially the same feature set. You can take the Docker path with code-server as well (https://hub.docker.com/r/codercom/code-server)
Moreover, they can install OpenVSCode Server to the cloud, and the project includes guides for running on AWS and Google Cloud, for the data science use case
Not sure this is a differentiating factor. code-server has guides for deploying to the cloud linked in the README: https://github.com/cdr/code-server#getting-started
Refer to this once, https://www.gitpod.io/blog/openvscode-server-launch
Another big difference between code-server and openvscode-server is that. code-server do support running locally without docker. This does offer a great personal / hobby development off of your main machine. While openvscode-server required you to tailor the Dockerfile to install necessary tools.
For short: I can use code-server (running natively) and use Tailscale to access my main machine with all the development tools ready to go. While with openvscode-server, I have to spin up Docker, install a lot of tools, reconfigure mount and ssh forwarding, etc... just to get started.
It is some major differences I can see out of the box.
