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
..
2016-11-25 18:19:08 +00:00
2016-11-25 18:19:08 +00:00
2017-01-16 18:56:55 +01:00
2016-11-25 18:19:08 +00:00
occ
2016-11-25 18:19:08 +00:00
2016-11-25 18:19:08 +00:00
2016-11-25 18:19:08 +00:00
2016-11-25 18:19:08 +00:00
2017-01-16 16:32:16 -05:00
2016-11-25 18:19:08 +00:00