Love the minimalism.
I've been working on a draft detailing my setup. It's very similar to yours, except the client-side is a Chromebook, running stock ChromeOS, and, therefore, 99% of my projects are on remote dev servers.
On the server-side, it is just vim, docker, and few other tools. Although, my vim config is a bit more than 10 lines; mainly plugins for Go, Rust, JS, & hashicorp tools.
I would love to hear about that. I'm very curious about developing on a Chromebook, particularly anything that lets you keep the security aspects but develop locally.
That's been my number 1 principle in a Chromebook setup: keeping ChromeOS security model in tact, while having flexibility to develop locally/offline when absolutely needed, though I've never been in a situation that forced me to be completely offline, thanks to tethering to my mobile network.
I'll share the link to my article once I've published it. 🙂
Love the minimalism.
I've been working on a draft detailing my setup. It's very similar to yours, except the client-side is a Chromebook, running stock ChromeOS, and, therefore, 99% of my projects are on remote dev servers.
On the server-side, it is just vim, docker, and few other tools. Although, my vim config is a bit more than 10 lines; mainly plugins for Go, Rust, JS, & hashicorp tools.
I would love to hear about that. I'm very curious about developing on a Chromebook, particularly anything that lets you keep the security aspects but develop locally.
That's been my number 1 principle in a Chromebook setup: keeping ChromeOS security model in tact, while having flexibility to develop locally/offline when absolutely needed, though I've never been in a situation that forced me to be completely offline, thanks to tethering to my mobile network.
I'll share the link to my article once I've published it. 🙂
Took a while, but finished the article 🙌
dev.to/petermbenjamin/a-minimal-ch...