My Macbook does throttle a lot and gets pretty hot when working on a fairly large codebase in TypeScript. Should be enough, right? While working, most of you have other stuff running Slack or other chat apps, an email client, your browser (most webdevs have several running at once), a music player. It has an Intel Core i7 and 16 GB of RAM.
My main development machine is a Macbook Pro 13'' from 2019. Resources a fairly complex webapp can contain a lot of files and do a lot of resource hungry stuff.Why would you want to run VSCode from a server? Nice bonus you can completely fence the VM behind a firewall and still have SMB access. Your development machine will be available from a local network. This makes it easy to connect without the need to change local configuration each time you start the server and it gets a new IP-address. Your development server will connect to your Global Area Network using ZeroTier. If you ever worked from VSCode on Windows with locally running containers or WSL it's exactly the same. Code completion, 'go to definition', debugging, running your code, even the terminal, it's all the same. You can connect your local VSCode editor with the VSCode server using SSH. From my experience working with this setup is almost the same as running VSCode on your own machine, except it's not on your local machine. You could probably use it for other stacks. You do not need Azure, you can also use this guide on a VM on a home-server, any other cloud provider or a VM provided by your employer.Īfter following these steps, you'll end up with a development server which you can use to work on Node.js frontend and backend projects. In this article I'll explain step-by-step on how to create your own VSCode server running on a VM in Microsoft Azure.
0 kommentar(er)
