Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

VS Code in the Browser for Everyone

gitpod.io

Post reply on HN
Print view View original

11–20 of 22 posts

Re: VS Code in the Browser for Everyone

#11

Post by tomvault »

chenzhekl wrote: post #7

Pretty cool project. I am wondering how it is different from code-server [1]? [1] https://github.com/cdr/code-server

Johannes here from Gitpod. Shared some background about differences on Twitter already: https://twitter.com/jolandgraf/status/1442850063953313805?s=...

Essentially, we run nightly builds at OpenVSCode Server making it as upstream to VS Code as possible. In contrast to other forks the whole scope of the project is to add a minimal set of changes (specifics about what we added https://github.com/gitpod-io/openvscode-server/blob/main/doc...)

The architecture we use powers both Gitpod and GitHub Codespaces. Several of the devs and organisations that have asked for our implementation & now have adopted OpenVSCode Server referenced the following issue at Code-Server (https://github.com/cdr/code-server/issues/3835).

Re: VS Code in the Browser for Everyone

#13

Post by tomvault »

orsenthil wrote: post #8

Is it for projects which are not hosted on github, which can be accessed using github.dev?

github.dev is solely the VSCode frontend/editor without access to any compute. OpenVSCode Server allows you to run VS Code on a remote machine and access it with a thin client through the browser. Unlike github.dev you get full access to the underlying OS and can run tests, compilation, install dependencies etc.

Re: VS Code in the Browser for Everyone

#14

Post by schainks »

mikewhy wrote: post #9

I looked into this when setting up a new machine. Well, not exactly openvscode but code-server. I have the same questions I had when investigating that: - with docker, how would you install eg. node and go binaries? - with docker, how would you set up some dotfiles? - how do you map remote ports to your local machine? I ended up going with VSCode Remote (SSH), and am loving it. But I still think I'd be happier with a…

Could you say more about your set up? I'm looking for something similar.

Re: VS Code in the Browser for Everyone

#15

Post by makethetick »

mikewhy wrote: post #9

I looked into this when setting up a new machine. Well, not exactly openvscode but code-server. I have the same questions I had when investigating that: - with docker, how would you install eg. node and go binaries? - with docker, how would you set up some dotfiles? - how do you map remote ports to your local machine? I ended up going with VSCode Remote (SSH), and am loving it. But I still think I'd be happier with a…

I have a similar setup, I use Caprover as a nicer way to manage docker. You can build whatever you want into the dockerfile then just map the user directory to a local one and port forward where needed.

If you want to run a web app through a domain with SSL then it's trivial to setup a nginx proxy container.

It takes minutes to spin up a new dev environment with everything setup out of the box including environment variables and access tokens.

Re: VS Code in the Browser for Everyone

#16

Post by throwaway284534 »

tomvault wrote: post #11
chenzhekl wrote: post #7

Pretty cool project. I am wondering how it is different from code-server [1]? [1] https://github.com/cdr/code-server

Johannes here from Gitpod. Shared some background about differences on Twitter already: https://twitter.com/jolandgraf/status/1442850063953313805?s=... Essentially, we run nightly builds at OpenVSCode Server making it as upstream to VS Code as possible. In contrast to other forks the whole scope of the project is to add a minimal set of changes (specifics about what we added https://github.com/gitpod-io/openvscode-se…

Hey! Thanks for the explanation, but I don’t fully understand the two projects. Is this built with code-server, or do the server parts of Gitpod come from Microsoft? Where should I submit PRs?

Re: VS Code in the Browser for Everyone

#18

Post by mikenikles »

throwaway284534 wrote: post #16
tomvault wrote: post #11

Earlier quoted context omitted.

Johannes here from Gitpod. Shared some background about differences on Twitter already: https://twitter.com/jolandgraf/status/1442850063953313805?s=... Essentially, we run nightly builds at OpenVSCode Server making it as upstream to VS Code as possible. In contrast to other forks the whole scope of the project is to add a minimal set of changes (specifics about what we added https://github.com/gitpod-io/openvscode-se…

Hey! Thanks for the explanation, but I don’t fully understand the two projects. Is this built with code-server, or do the server parts of Gitpod come from Microsoft? Where should I submit PRs?

Hi, Mike from Gitpod here. This project does not use code-server. It is instead a very lightweight server added to the official open source VS Code repo from Microsoft.

We documented this in more detail in the "Source Code Organization" chapter at https://github.com/gitpod-io/openvscode-server/blob/main/doc....

As to where to submit PRs:

- Anything to do with running VS Code in a server context: gitpod-io/openvscode-server

- Anything else related to VS Code: microsoft/vscode

We have no intention of changing VS Code in any way or to add additional features to VS Code itself.

Re: VS Code in the Browser for Everyone

#19

Post by [deleted] »

makethetick wrote: post #15
mikewhy wrote: post #9

I looked into this when setting up a new machine. Well, not exactly openvscode but code-server. I have the same questions I had when investigating that: - with docker, how would you install eg. node and go binaries? - with docker, how would you set up some dotfiles? - how do you map remote ports to your local machine? I ended up going with VSCode Remote (SSH), and am loving it. But I still think I'd be happier with a…

I have a similar setup, I use Caprover as a nicer way to manage docker. You can build whatever you want into the dockerfile then just map the user directory to a local one and port forward where needed. If you want to run a web app through a domain with SSL then it's trivial to setup a nginx proxy container. It takes minutes to spin up a new dev environment with everything setup out of the box including environment v…

[deleted]
Post reply on HN