Conor Anderson 18d29d7dbf Be noisy about updating permissions ...

In #75, I mentioned that I was a little stumped why my Nextcloud container was showing a `502 Bad Gateway` error. In the end, it turned out that it was just updating the permissions in the container, which are set to `nobody:nogroup`, but need to be chowned to `991:991` when first starting a fresh container. This PR seeks to make that a little more obvious to the user, in case they choose to use `docker-compose logs -f nextcloud` or such.

2017-01-16 16:32:16 -05:00

boinc

update dockerfiles, clean up

2017-01-16 22:13:29 +01:00

boring-nginx

update dockerfiles, clean up

2017-01-16 22:13:29 +01:00

cowrie

update dockerfiles, clean up

2017-01-16 22:13:29 +01:00

ghost

update dockerfiles, clean up

2017-01-16 22:13:29 +01:00

isso

update dockerfiles, clean up

2017-01-16 22:13:29 +01:00

lychee

update dockerfiles, clean up

2017-01-16 22:13:29 +01:00

nextcloud

Be noisy about updating permissions

2017-01-16 16:32:16 -05:00

piwik

update dockerfiles, clean up

2017-01-16 22:13:29 +01:00

privatebin

update dockerfiles, clean up

2017-01-16 22:13:29 +01:00

rtorrent-flood

update dockerfiles, clean up

2017-01-16 22:13:29 +01:00

searx

delete all root process

2016-09-16 17:08:06 +02:00

subsonic

update dockerfiles, clean up

2017-01-16 22:13:29 +01:00

tor

update dockerfiles, clean up

2017-01-16 22:13:29 +01:00

unmaintained

update dockerfiles, clean up

2017-01-16 22:13:29 +01:00

LICENSE

initial commit

2016-04-11 15:59:32 +02:00

Description

Mirror of github.com/hoellen/dockerfiles

boringssldockermatomonextcloudnginxprivatebinserver

CC0-1.0 2.3 MiB

Languages

Shell 46.5%

Dockerfile 39.4%

Roff 10.9%

PHP 1.8%

SCSS 1.1%

Other 0.3%