3 ms·
I'm a big fan of this approach and do similar! If it's something I only need when I'm at my computer and where I'm fine if it falls over then I'll host on local
by bluehatbrit 4y ago
I'm a big fan of this approach and do similar! If it's something I only need when I'm at my computer and where I'm fine if it falls over then I'll host on localhost. I then have a small Lenovo M700 Tiny which I use to run things I may want on multiple devices (use Tailscale so I can access it remotely) but where I don't care too much if it falls over. Anything that I want to be really stable I run on my Hetzner dedicated.
It's great fun and I enjoy having the control over the few things I run. It's also super conveniant when it's running locally because I don't really have to worry much about securing the service behind reverse proxies and all that. I can just hit it however I like with any ol script.
It's not for everyone, but it works for me.
- bshipp 4y agoSame here! I read the headline and thought "isn't that what Docker is used for?" As soon as i opened the article I saw the author and I had the same idea, even down to using ufw-docker. I have individual ports scripted to open with ufw-docker after docker-compose is run. I know docker isn't the best tool for every task, but I very much enjoy how it allows me to treat my laptop and my cloud servers as almost identical machines and compartmentalize my services.
- bluehatbrit 4y agoYep! Containers are really great for this kind of thing, it's so trivial to run basically anything as long as the configuration docs are reasonable. I use a single node k3s cluster on my lenovo box (for learning) and just straight up docker-compose on my localhost and dedicated because it's just so easy.