I default to Docker Compose not because I love Docker, but because I never want to mess with a local install of Postgres, Redis, MySQL, or whatever new thing comes out. I don't want to spend any time provisioning or caring about any of these services and Compose just works for me.

As a long-time user, I don't really use pending todos. Several of mine are from projects I gave up during the pandemic and never got around to cleaning them up.

I can see why people like them, but 99% of mine are in GitHub Issues and I try to remember to come back and do a post update here.

Homebrew and 1Password.

In case it's useful, here are my Default Apps as of a few months ago: jefftriplett.com/2023/default…

I have never used cap but I have used resources with limits + reservations via compose which should just be passing those through as cli options: docs.docker.com/compose/compo… - I would ChatGPT this to see what args are 🤣

80% of 90% should be good enough to keep control of the box. I'm lazy and I have two or three dozen containers running without issues on a 4 GB droplet. Worse case, you can narrow it down to the service.

Thanks for the update. I haven't looked at Kamal in much detail, but it looks like a wrapper around Docker.

I use Docker and Compose a lot, and assuming Kamal allows you to pass through extra options, you should be able to throttle the CPU/memory to keep a process from running away with your droplet. That might be worth in case you keep seeing spikes. It won't limit the appearance of downtime for that service, but it'll keep the box and other containers running.

Also, if you aren't running DO's managed databases, please save yourself some grief and do that vs. trying to run it in Docker.

Digital Ocean VPS or Hetzner + Cloudflare is hard to beat.

I have run dozens of containers on DO droplets for years, and they are hard to beat. I heard equally good things about Hetzner (I'm also told they are cheaper).

Use the query string trick of adding ?asdf or something to the URL of your image and they should re-fetching the newer image.

You don't need one, but it's a non-zero trade-off if you get big enough to sell. So, it's not a blocker, and we can't predict success. I'd focus on the idea and build it out, and if you have enough money that you don't know what to do with, then pursue a .com is a good way to fill your week 🤣

I converted from Buffer to Typefully because I like the IDE and scheduling tool better than anything else. Typefully has good X/Twitter integration but also supports Mastodon and LinkedIn.

They also support Zapier which helped me post to Mastodon for a year or so before they added native support. So Zapier can probably get you anything that's missing or you could use their webhook to roll your own.