option to change caching inside the container?

[r2evans]

(I am not intending to get into a debate of apache-vs-nginx.)

I'm trying to incorporate your postgresql, owncloud, gitlab, and redis containers with both docker-gen and eventually letsencrypt (long-term goal). The point of using docker-gen here is to provide, via automated virtual host configuration, an installation of nginx (either host- or container-based) that provides virtual-host access to the containers' services.

I don't know what problems there would be with double nginx cache proxies ... I think it could certainly be problematic (highly inefficient at best), and though it's certainly possible to disable caching on one of them, the easiest place to change things would be on the host-based nginx, and caching all virtual hosts except one is just unnecessary complexity.

So there are two alternatives, both of which suggest providing options within your container configuration.

1. Allow apache2-based configs, where it uses (likely) mod_php instead of php-fpm.
2. Add an option that tells the nginx instance internal to the owncloud instance to do no caching.

The second option appears to me to be the simplest.

Do you see value in providing this type of configurability?

(Thanks for your multiple containers, btw! Having a good example of "docker-compose" is also very useful.)

Edit: perhaps this is what NGINX_PROXY_BUFFERING and company do in your gitlab container?