Code-Server: Developing on Your Server with VS Code in the Browser

Code-Server runs VS Code on the server and streams the UI to your browser. Because the code, dependencies and running processes stay on the server, closing your laptop does not stop the work; you can pick up the same session from a phone or another machine. In exchange there is exactly one thing to be careful about: this UI grants access to every file on your server and to a terminal.

Setting the password#

Code-Server reads the password from the PASSWORD environment variable. Open the service detail page in the panel, set it under 'Startup Variables', and restart the service. Keeping it in an environment variable rather than a file on disk prevents it leaking into your backups and version control.

# 32 karakterlik rastgele parola
openssl rand -base64 24

# Windows PowerShell alternatifi
# [Convert]::ToBase64String((1..24 | %{ Get-Random -Max 256 }))

Your own domain and HTTPS#

Connecting to Code-Server over IP:port works, but your traffic is unencrypted -- your password and the code you type travel in plain text. On top of that, some browser features such as clipboard access and service workers only work in a secure context (HTTPS). Attaching a subdomain from the Domain card on the service detail page gives you HTTPS through Cloudflare.

Day-to-day tips#

• Extensions come from the Open VSX registry; Microsoft's proprietary extensions (e.g. the official C# extension or Pylance) are not available there for licensing reasons, so use open-source equivalents.
• Ctrl+Shift+P can collide with browser shortcuts; press F1 instead when the browser swallows the key.
• Run long jobs inside tmux or screen rather than the integrated terminal, so closing the tab does not kill the process.
• Watch the service disk quota: node_modules and build output grow faster than you expect.