As a programmer who relies on VS Code, I’ve found that self-hosting a Code-Server fork is crucial to my computing setup. Here are the top reasons why.
1. Centralized Programming Workstation
I host my own Code-Server instance on my dual Xeon workstation, allowing me to access it from any machine over my local network, including devices with limited compatibility with VS Code.
2. Reduced File Clutter
By storing all code files on a centralized server, I no longer have to clutter my Single-Board Computers’ microSD cards with project files, making organization and switching between devices much easier.
3. High Availability and Backup Protection
Code-Server’s high-availability setup and daily NAS backups ensure that my work is safe and sound, even in the event of a server failure or hardware issue.
4. Seamless Device Switching
With Code-Server, I have the same coding environment regardless of the system, eliminating the need to install extensions on each device.
5. Power and Performance
Code-Server can handle powerful, centralized servers with ease, making it an excellent choice for devices that require a lot of firepower, such as RISC-V machines.
6. Access to Limited Devices
While VS Code is not available on smartphones and tablets, I can still access my code files using Code-Server on these devices, thanks to its web-based interface.
7. Open-Source Extensions
Although the Extensions Marketplace isn’t open-source, Code-Server relies on the Open-VSX Extension Gallery, which includes most of my favorite extensions, although some notable options remain inaccessible.
Source: https://www.xda-developers.com/code-server-changed-my-workflow