![]() ![]() There are several ways to setup code-server:ĭue to simplicity, I am preferring to use the shell script installation method together with the Caddy server. It sounds like exactly what I need, I decided to give it a try. Run VS Code on any machine anywhere and access it in the browser. Since I didn’t find an appropriate official solution, I did a bit of investigation and found a tool called code-server ( ). Additionally I’m often in a position to have very cheap instances so this wouldn’t make sense in a financial way as well. This sounds better, but I would rather like my machine fully managed by me. In a nutshell, it’s GitHub’s SaaS that provides VS Code on demand for a per-hour-based pricing model. Visual Studio Code backed by high performance VMs that start in seconds. Honestly, I don’t know much about this and I’m not sure if it existed at the time when I investigated this concept last year, but GitHub describes it as:īlazing fast cloud developer environments ![]() ![]() There is another interesting solution today called GitHub Codespaces. This means that I wanted to be able to access it from the browser, from any computer without the need to install any additional dependencies like VS Code, SSH client, or similar. While all these implementations can be very handy, they were not suitable for my use case since I wanted my VS Code environment completely independent from my workstation. Develop in Containers – Run Visual Studio Code in a Docker Container.Work in WSL – Run Visual Studio Code in Windows Subsystem for Linux.Remote via SSH – Connect to remote and virtual machines with Visual Studio Code via SSH. When it comes to remote code execution, Visual Studio Code officially provides three ways to achieve this: I was actually surprised with the number of possible solutions for this problem, and in this article, I’m going to share the process that I used (and I’m still using) to set up VSCode and JetBrains IDEs on a remote machine. These dynamic circumstances finally pushed me to find a solution that is decentralized, stable, and accessible. The second problem was the degradation of internet connection and DNS, due to the sudden high demand for internet bandwidth. The first problem was the fact that I was working from several locations on a few different machines due to ever-changing lockdowns. The moment when I realized that I definitely need a remote dev environment was last year, at the beginning of the Covid-19 crisis. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
January 2023
Categories |