Should we have nginx as a separate container?

[usabilla]

Should we have nginx as a separate container?

[renatomefi]

I rather have them together, losing unix socket in pro to have a more granulate architecture is not an advantage imho.
We either deliver web or interact-less (cli) PHP applications, I don't see advantage on scaling fpm and not nginx or vice-versa

[lcobucci]

The trade-offs of that particular scenario are (as far as I can tell):

1. having to have supervisord (or any other pkg) to ensure that services are running
2. consolidating logs from nginx, php-fpm, and app using the same format in a consistent way is a bit more challenging

What are the ones involved on splitting things (apart of losing unix sockets)?

[renatomefi]

After talking with @stevenjm :
As long as we manage to keep both containers in the same namespace we can share the socket and have "no" performance degradation, so this should be considered when deploying php and nginx containers imho

[lcobucci]

As long as we manage to keep both containers in the same namespace

I think this is a must anyway, we already decided that every pod will have all containers to run the application.

@stevenjm @renatomefi could you give us some examples of nginx configuration that allow us to achieve that? I assume that this is the main point:

fastcgi_pass   unix:/var/run/php7.1-fpm.sock;

[frankkoornstra]

Adressed in #30