[nkmnz]

Could I use this for running the same docker compose stack multiple times in parallel? I wrote a lot of bash glue code to make this happen (without kubernetes) for integration and acceptance testing on a single server. Managing envs and networking was a pain, but mostly, I struggle to keep it up to date with infrastructure changes in my platform.

[bewuethr]

Have you tried Tilt? https://tilt.dev/

[nkmnz]

No, I haven't. Can you elaborate how you think it could help me? Couldn't figure it out from reading the docs, tbh.

[SOLAR_FIELDS]

Tilt is great but it doesn’t solve the problem you’re asking about. This project more directly addresses that. Fundamentally the problem is that you want to maintain the lifecycle of several services during an ephemeral ci run and tear them down when you are done. As you mentioned it gets unwieldy and annoying to try to run all of these on a single machine and doubly so when you have a lot of services/containers. Kubedock is more like what you are looking for, it translates compose calls to Kube equivalents and each service in the compose file is it’s one kube pod with its own lifecycle. It should be possible under that to do what you are saying, spawn multiple docker composes from a single run.

It is worth noting that Kubedock has some really annoying limitations, part of it is that it’s one person the other part is that some concepts don’t translate to kube very well. So make sure that whatever you will be doing fits into those constraints before you try it

[mlnj]

I love Tilt.

With a single Tilt file combined with a docker compose file, almost all of the infrastructure you need is configured on a local machine. It also supports running kubernetes (most of the docs are around this), but you do not necessarily need to it it.My goto when I have more then 2 docker containers/services I want to keep changing code for. Some teams I work with usually have 20 such containers for local dev.

And yes, you can even nest Tilt files and even write normal python if you want to mix things up.

[sandGorgon]

yes. fixing this right now. you will have it in a day or two.

[nkmnz]

Would certainly try this out!

[sandGorgon]

this is done. Please feel free to try that.

Also, btw - kappal is architected AI first. Meaning: 1. we have a beautiful skill that can be used by Claude 2. The help command generates output that is useful for claude 3. we have a "kappal inspect" command that generates live output of the stack that can be used by Claude.

hope you have a great time using it. Please file bugs!

[nkmnz]

Might take a couple of days until I have time to try, but certainly will!