Configuration folder & sites configuration as mountable volume about nginx HOT 7 CLOSED

I've been getting by in plushu/plushu-container by mounting my Nginx conf volume in /usr/local/nginx/etc and just explicitly specifying the location with -c.

If this is proposing setting the default prefix to /etc/nginx and the default config to /etc/nginx/nginx.conf, I'm all for that (it'd be one less thing to specify and one less difference I'd have to worry about between running my configuration in a container vs. on the host).

I don't know anything about the default nginx.conf or sites-enabled, I don't use either of those. (https://github.com/plushu/plushu-nginx-container/blob/master/install should give a fair idea of what Plushu's Nginx setup looks like)

from nginx.

I like moving the conf files to their own folder in /etc. We should incorporate this idea into the other base images so that configuration is easier to override, esp given moby/moby#6011.

from nginx.

I second this. In fact I tried to get it in a pull request way back but then it was of no interest for some reason.

Happy to see it coming anyways.

from nginx.

Here's what I use: felixhummel@a06716a

Interesting bits

--conf-path=/etc/nginx/nginx.conf
--prefix=/nginx

And the run looks like this:

docker run \
    -v /some/data/dir:/nginx \
    -v /config/dir/etc:/etc/nginx \
    nginx:latest

Not perfect, but works for me. I guess we need some best practices / standards guide for those kind of things. /nginx seems like a hack to me, but I wanted it separate from the config.

from nginx.

Assuming /nginx contains your site pages etc, maybe use /var/www or /var/www/html?

from nginx.

1. conf-path and prefix should be separate, because
   • include foo.conf then refers to $(dirname $conf-path)/foo.conf for configs and
   • root bar refers to $prefix/bar for static data
2. conf-path should be /etc/nginx/nginx.conf to allow mounting of /etc/nginx or putting those configs in the container
3. prefix should then be /var/www (Debian-style), which could be mounted completely or split up into /var/www/site_a and /var/www/site_b

See also http://nginx.org/en/docs/configure.html

from nginx.

So, the new images will have /etc/nginx/ volume and should be up on the hub in the next 4-5 hours.

Nginx upstream will now be providing and maintaining the images nginxinc/docker-nginx.

from nginx.