Mastodawn

On one system, I'm moving from an AMI bake approach (bash script that installs everything on a server, generate an image of the disk, use that to spin up instances) to using docker containers on the same servers. Then the disk image can be way more generic: install docker & run docker compose against a compose.yaml in user data. Nice benefit is I can now do in-place updates easily and very quickly.

Anyone else using this approach? I might blog about it if anyone's interested.

#webdev #docker

Show thread

Kai, sounds like the sky Feb 22

@JesseSkinner incidentally this is how Atlassian deploys their stuff, but they’re backwards savages when it comes to infra and half of their services are perpetually broken because of that

Just do containers on ECS instead. That’s acutely the golden path at AWS

Show thread

Jesse Skinner Feb 22

@kaievans I'm getting these off AWS on onto OVH, which is the primary motivation for moving away from AMIs. On OVH I think I'd have to use Kubernetes to do something like this. Hence the roll-your-own approach, since I think the complexity of k8s will be overkill here.

Show thread

Kai, sounds like the sky Feb 22

@JesseSkinner it’s your systems, Jesse, but if you want an opinion, not containerising one’s production software in 2026 is akin to moral failure ;)

Also in my experience people who say “kubes is an overkill here”, temd to write hundreds of lines of barely maintainable bash code and regularly ssh into their hosts to play whack a mole with their snowflake setups

Sorry a bit abrasive, but I mean well :)

Show thread

Jesse Skinner

@kaievans I definitely appreciate the push. Of course *my* hundred line bash scripts are fantastic ;) I'll think about what you said and might give kubes a try here.