Eric Kidd

There are several general categories of things we might want to watch or monitor in a typical development session: - Project-level source code in `pods` and `config`. - Container source...

This is an excellent question! The short form of this answer is that the same source tree is often used by multiple pods: If you want to change `rails_hello` in...

That's a nice idea, and I'll save it for future prioritization. Note that `cage mount frontend` might pull source code multiple services all at once. I'm not sure that most...

Ah, OK, that does make more sense. So in order of lookup: - `rails_hello` - `frontend/web` - `web` (if unique) The latter two would actually just map to `rails_hello` internally,...

Ah, OK, so you're also suggesting the idea of moving `mount` from the `source` subcommand to the top level, perhaps with different semantics for the two?

I think the "standard" way to handle this in `docker-compose` is using the `dockerfile:` parameter, maybe? ```yaml dockerfile: subdir/Dockerfile ``` It might make sense to extract `subdir` from there? I...

Ah, wait. It looks like `dockerfile` doesn't do what we want. Sorry. :-( It looks like we would need to figure out that syntax for in-repo paths in Git URLs,...

Yes, this would be an excellent and 100% acceptable solution! In general, any time we can implement a feature by improving our support for `docker-compose` and `docker` features, it's got...

Yeah, we have a mix of ECS and Kubernetes on the backend, but we usually wait until new Docker features are deployable on ECS to really start experimenting with them....

Yeah, definitely in `dc::GitUrl`. The goal of `compose_yml` is to be the sole authority for everything related to parsing `docker-compose.yml` files. This is another lesson we learned the hard way:...