3 ms·
I am sorta doing this, locally. I have a handful of servers in my basement that I use vscode+remote-ssh to work with. The benefit is that I can jump from my des
by whalesalad 3y ago
I am sorta doing this, locally. I have a handful of servers in my basement that I use vscode+remote-ssh to work with. The benefit is that I can jump from my desktop to my laptop without any fuss. I can leave long-running scripts online for like an experimental batch job and attach to that from any machine, even when I am not home thanks to wireguard/tailscale. It is very nice knowing my dev env is always there in the state I last left it. This also gives the nice benefit of being able to choose your developer env (windows or mac) while running your dev/code/system on a linux system for example. It also gets you around architecture issues, like if your laptop is arm-based and your app needs x86.
I was initially kinda opposed to this and preferred "bare metal development" on my local rig. But the performance is actually pretty incredible for remote development with vscode such that I don't really notice things are running on different hardware.
We recently had some new members join the team and I decided to spin up some dedicated EC2 instances for them to use for this exact purpose. They aren't being used yet, but as our stack becomes more sophisticated I think workloads will transition there. It's done with a custom terraform module that also provisions other assets needed for each dev (regardless of local or remote dev) like an S3 bucket, some dynamo tables, IAM roles, etc. Being able to onboard a new dev with a handful of lines added to a mapping is pretty awesome.
tl;dr I would absolutely consider remote dev spaces.
- nickstinemates 3y agoThis is basically what I do as well. It's awesome.