Hacker News Reader

> web:

> <<: default-app

> ...

> worker:

> <<: default-app

This is always somewhat of a code smell to me. This makes me want to dig deeper and see if the two use cases shouldn't have been separated into separate Docker files or even separate apps.

View on HN

It seems reasonable to me (for a compose-in-prod setup). The standard setup (at least for Rails, in my experience) is that the web server and background job processor will have the same dependencies and nearly identical configuration. Until the app has gone off the rails and I really do need to have the server and worker diverge, this approach seems like less to worry about than maintaining multiple images and duplicated but 98% identical container definitions.

Yeah, same with Django ... really try to keep these environments all in sync so you don't have different environments for no real gain. What do I gain when my worker doesn't have django-allauth installed other than possible development environment complexity.

I tend to start with monolith and split things out when I get frustrated with how coupled they are.

Reply on news.ycombinator.com