David Heinemeier Hansson

Feel free to look into that @jacoscaz

I like the idea of having the role be part of the container name 👍. Need to ensure "web" is default when there's nothing else.

You shouldn't have multiple containers of the same role running on the same server. Don't want to support that. Concurrency needs to come from each of those containers internally (WEB_CONCURRENCY...

They're the same service, because they're running the same image. If they run a different image, they're an accessory.

Don't want to add configuration flags until we have a proven case that details how we can't do without. Every configuration point is cognitive overhead. It should be there because...

Yeah, I but that the new naming becomes: `service-role[-destination]`. So `hey-web`, `hey-web-staging`, `hey-jobs`, `hey-jobs-staging`.

Yes, happy to see it. I've been thinking about how to do it. Will require some rejigging. But if anyone wants to take it on, have a swing. Just use...

I like the idea of current. Don't think you need CurrentAttributes, though, since there's no resetting needed. Because it is indeed a bit of a hassle to pass the role...

I dig this. The error messages aren't super friendly out the box, but it's better than what we have now: which is half baked! Please do continue 👍

Awesome. Will check it out now. Yes, we just had an issue this morning at 37s because of lacking schema validation 😄