VSCode Server: Ability to run vscode-server as a daemon in the server and other feedback

[tvvignesh]

Hi. I have started using VSCode Server today and I should say its really awesome. One thing I feel is missing is that, the code-server cli could offer users an ability to run code-server as a daemon/background process in the host machine and also auto start on reboot rather than users figuring out how to do it themselves.

This will create a workflow where you just boot the system, open the browser and start coding

Also, I don't see any information on validity of the tunnel in the docs. If a server is started and tunnel is created, is it valid forever till we stop the server? Also, I don't see any docs on whether this would be charged separately when out of preview or is it meant to be free forever?

And, when I want to open up VSCode windows locally, I typically do code . against a folder but when doing that in the browser, the desktop version of VSCode opens up. Is it possible to open browser based VSCode when doing code . or can there be alternative command to just trigger open new VSCode tabs in the browser opening the respective workspace?

In future, it would be great if there was a developer dashboard where I can start/stop/manage VSCode servers against different instances and open VSCode windows directly from there.

Thanks a lot again for making VSCode awesome. I will drop more feedback as I use VSCode server more.

[GuillaumeASSIER]

Have you tried to create a systemd service for code-server?

[tvvignesh]

@Sykursen Yup. That works. Just left the feedback for other users. Also, was not sure how long the auth is valid, so added that as well

[tanhakabir]

Hello! Thanks for the feedback!

could offer users an ability to run code-server as a daemon/background process

Yes this is a great idea and planned for the upcoming iteration!

Also, I don't see any information on validity of the tunnel in the docs. If a server is started and tunnel is created, is it valid forever till we stop the server?

The tunnel should stay open forever until you close it your your system shuts down

Also, I don't see any docs on whether this would be charged separately when out of preview or is it meant to be free forever?

This is planned to be free

And, when I want to open up VSCode windows locally, I typically do code . against a folder but when doing that in the browser, the desktop version of VSCode opens up. Is it possible to open browser based VSCode when doing code . or can there be alternative command to just trigger open new VSCode tabs in the browser opening the respective workspace?

This is a good feature request as well. Would you mind creating it in the vscode repo?

[tvvignesh]

@tanhakabir Sure. Will create an issue and update here

[jcouball]

@tvvignesh would you mind sharing your systemd unit file for code-server? I am not well versed at systemd so this would save me some time and help me learn. I would appreciate it very much.

[tvvignesh]

@jcouball Sure. This is what I used. Just remember to replace the user and group name

/usr/local/bin/codeboot.sh

#!/bin/sh
code-server

/etc/systemd/system/code-server.service

[Unit]
After=network.target

[Service]
User=<yourusername>
Group=<yourgroupname>
ExecStart=/usr/local/bin/codeboot.sh

[Install]
WantedBy=default.target

[SpyderHunter03]

I may be in a minority here, but what would the process be to make this a service on Windows machines? I love having it available, but I don't want to keep a powershell window open all the time.

Also, does VS Code Server keep running if my computer goes to sleep or at least to screensaver? I wouldn't imagine that it would remain running if the computer goes to sleep, but I feel like it should/could if it goes to screensaver.