3 ms·
This is what I do 99% of the time (unless I drastically feel the need for a visual debugger as I'm not so familiar with CLI debugging just yet). I run a dev VM
by ar_lan 5y ago
This is what I do 99% of the time (unless I drastically feel the need for a visual debugger as I'm not so familiar with CLI debugging just yet).
I run a dev VM on any machine(s) I'm actively working on that all share the same setup - today, that's my Macbook and my desktop at home. They aren't necessarily in sync, but they do share the same dotfiles and versions of everything, so if I want to switch my dev work all I simply need to do is a `git pull` on whatever project I'm working on, and then everything is caught up between the two.
With this, I just `mosh dev` (and then straight into `tmux`) on whatever computer I'm running into and just use `vim` for everything. If I really need a graphical debugger I can always open the VM graphically, but that's so rare that it hardly feels worth mentioning.
- rank0 5y agoHell yeah! I wish more folks would appreciate how flexible and feature rich the old school cli tools can be. What’s your VMM setup? I just edit right on the remote machine. Lately I’ve been playing around with lxd/lxc for persistent container dev environments. This way I can avoid the VM overhead and it “feels” the same…but I have yet to fully explore this approach.
- ar_lan 5y agoI'm running a NixOS VM. I've tried to dockerize it before but inevitably something always failed - with the VM approach it is always much more stable. I just run it right in VMware Fusion / Workstation, and it works great. Extremely reliable, very low overhead still. It just takes a lot of storage is all :) But everything is always reproducible given the nature of the VM, without needing to pass around snapshots or clones.