codinglog

Picking the Cloudflare stack for the new project. The traffic profile is all or nothing: if it takes off it can see millions of hits a day, and if it doesn't it gets none. Setting up for that on AWS or a VPS with Kubernetes means building the scalable deployment upfront, time spent before knowing if the project even works. Instead I'm going with Cloudflare Workers, R2 for images, and KV, starting on the $5/mo Workers plan. The frontend goes on Cloudflare Pages, so that's served through the Cloudflare CDN as well. Not saying $5 covers all the scale, just the start. After that it stays cheap for what it is, and more hits means more revenue, which is easy to pay. What I'd rather avoid is setting up something on a VPS that needs to be scalable upfront for a site this uncertain. No k8s to babysit either way.

Working on a Docker compose companion tool which can help me stay up-to-date with the containers and help me get alerts and debug if something goes off rails.

I need to setup a password manager to keep track of my projects' credentials. Right now they are spread across so many places. Some in notes, some as files, some in .env, and some actually in a password manager. No idea what's where anymore. Also the links and details of all projects are getting out of hand. Which VPS, which domain, what renews when, where's the login. Need to plan something for these as well.

Testing Dockhand on my local, looks very interesting. Good UI, does almost everything a docker management tool needs to do, also feels simpler to use than Portainer CE. Will share more when I find any more interesting stuff about Dockhand.