Use www-data user instead of cloudron

CloudronManifest.json

@@ -37,6 +37,6 @@
   "changelog": "file://CHANGELOG",
   "postInstallMessage": "file://POSTINSTALL.md",
   "optionalSso": true,
-  "minBoxVersion": "1.8.1",
+  "minBoxVersion": "4.0.0",
   "documentationUrl": "https://cloudron.io/documentation/apps/wordpress/"
 }

Dockerfile

@@ -26,7 +26,7 @@ RUN curl -L -o /app/code/disable-wordpress-core-update.zip https://downloads.wor
 # https://plugins.svn.wordpress.org/wp-mail-smtp/
 RUN curl -L -o /app/code/wp-mail-smtp.zip https://downloads.wordpress.org/plugin/wp-mail-smtp.0.10.1.zip
 
-RUN chown -R cloudron:cloudron /app/code
+RUN chown -R www-data:www-data /app/code
 
 # configure apache
 RUN rm /etc/apache2/sites-enabled/*

cron.sh

@@ -4,4 +4,4 @@ set -eu
 
 echo "=> Run cron job"
 
-exec /usr/local/bin/gosu cloudron:cloudron /app/code/wp cron event run --due-now
+exec /usr/local/bin/gosu www-data:www-data /app/code/wp cron event run --due-now

start.sh

@@ -3,7 +3,7 @@
 set -eu
 
 readonly WP="/app/code/wp --allow-root"
- 
+
 mkdir -p /run/wordpress/sessions
 
 # Detect the wordpress prefix from existing database. This is a bit of a hack because some wordpress plugins
@@ -165,7 +165,7 @@ EOF
     $WP --format=json option update authLDAPOptions "${ldapConfig}"
 fi
 
-chown -R cloudron:cloudron /app/data /run/wordpress
+chown -R www-data:www-data /app/data /run/wordpress
 
 echo "Starting apache"
 APACHE_CONFDIR="" source /etc/apache2/envvars