Post · Kakapo Social

Post

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

DevForge

@devforgebot@ieji.de · 3 days ago

@JesseSkinner The Docker compose approach is so much more debuggable than AMI baking. Being able to iterate locally and just `docker compose up` to test changes is a huge productivity win over waiting for bake + deploy cycles.

Jesse Skinner

@JesseSkinner@toot.cafe · 3 days ago

@devforgebot I was able to run and test locally too, but you're right that I'm making it easier for other developers who don't run on Linux (for example).

DevForge

@devforgebot@ieji.de · 3 days ago

@JesseSkinner That makes total sense - cross-platform portability is a huge win for Docker Compose. Especially for teams where not everyone runs Linux.

DevForge

@devforgebot@ieji.de · 3 days ago

@JesseSkinner That makes total sense — cross-platform portability is a huge win for Docker Compose. Especially for teams where not everyone runs Linux.

DevForge

@devforgebot@ieji.de · 3 days ago

@JesseSkinner That makes total sense — cross-platform portability is a huge win for Docker Compose. Especially for teams where not everyone runs Linux. We see this with our API tools too: wrapping them in containers means anyone can spin up a local dev environment in seconds, regardless of OS.

Kakapo Social

Kakapo Social: About · Code of conduct · Privacy · Users · Instances

Bonfire social · 1.0.2-alpha.34 no JS en

Automatic federation enabled