Update 'compose/certbot/init.sh'

Reviewed-on: #1

compose/certbot/init.sh

@@ -3,7 +3,7 @@ set -eu
 touch /var/log/letsencrypt/letsencrypt.log
 echo "Initializing certbot..."
 rsa_key_size=4096
-email=${ADMIN_EMAIL:-'admin@example.com'} # Adding a valid address is strongly recommended
+email=${ADMIN_EMAIL:-'admin@example.com'} # Valid address is required
 
 # Enable staging mode if needed
 staging_arg=$(test $CB_STAGING && echo "--staging" || echo "")

compose/nextcloud/Dockerfile

@@ -1,13 +1,10 @@
 FROM nextcloud:23-fpm-alpine
 
-ARG UID=1000
-ARG GID=1001
-
 RUN apk add shadow && \
- groupmod -g $GID www-data && \
- usermod -u $UID -g $GID www-data && \
- find / -user 82 -exec chown -v -h $UID '{}' \; && \
- find / -group 82 -exec chgrp -v $GID '{}' \;
+ groupmod -g 1001 www-data && \
+ usermod -u 1000 -g 1001 www-data && \
+ find / -user 82 -exec chown -v -h 1000 '{}' \; && \
+ find / -group 82 -exec chgrp -v 1001 '{}' \;
 
 RUN apk add --no-cache supervisor imagemagick-dev imagemagick \
   && mkdir /var/log/supervisord /var/run/supervisord \

compose/nextcloud/README.md

@@ -1,3 +0,0 @@
-# Permission
-If Nextcloud data is being placed in a docker managed volume, then `Dockerfile` can be updated by removing L6-L10 thus making the image smaller and not modifying the permissions for Nextcloud.  
-If Nextcloud data should be accessible from "bare metal system" as a specific user, then modify `Dockerfile` with correct `UID` and `GID` values.  

compose/nextcloud/entry_uid_change.sh

@@ -0,0 +1,6 @@
+#!/bin/sh
+
+find / -user 82 -exec chown -v -h 1000 '{}' \;
+find / -group 82 -exec chgrp -v 1001 '{}' \;
+
+/entrypoint.sh "php-fpm"