I haven been working on my own version of docker-compose that can also work with podman. But the draw for me here isn’t that i wanted to replace docker-compose, or even use podman specifically, but rather that I wanted to have a one stop shop for generating conteinerized projects using my most used languages and frameworks without having to have any tool chains installed locally, and as a bonus point have a wrapper to be able to issue commands inside those containers without having to use the full docker-compose incantations or having to shell into the running containers.

It’s not a full replacement, and I wouldn’t use this in production. It is more meant to help lower the friction for starting new learning projects.

Right now I can do things like `wizard new rails -d postgresql MY_PROJECT` or `wizard rust test` or `wizard start`

It is mostly cli for now but I’ve started working on a nice TUI for it as well.

No good reason for this other than not wanting to depend on environment managers, tool chain managers, or a combination of different tools.

I don’t use docker-compose for almost anything now, but projects generated with my tool are fully docker-compose compatible as I also create a docker-compose file when creating a new project with my tool. It’s been a really fun learning exercise and I learned a LOT about docker and the docker api in the process