Solved LAMP unbound variable MYSQL

[luckow]

What does

Mar 08 14:16:04 /app/code/start.sh: line 47: MYSQL_HOST: unbound variable
Mar 08 14:16:06 ==> Do not override existing index file
Mar 08 14:16:06 ==> Running custom startup script
Mar 08 14:16:06 ==> Imported crontab
Mar 08 14:16:06 ==> Creating credentials.txt

mean in an "infinite" loop? App is not responding.

[nebulon]

@luckow that LAMP app instance is outdated and has to be replaced by now. If you have a cloudron cli, then you can run cloudron update --app <appdomain> --appstore-id lamp.cloudronapp.php74

After that you have to potentially update the app, in case those env variables are used. Generally all Cloudron injected env vars are now prefixed with CLOUDRON_ to avoid potential env var collisions.

[nebulon]

@luckow that LAMP app instance is outdated and has to be replaced by now. If you have a cloudron cli, then you can run cloudron update --app <appdomain> --appstore-id lamp.cloudronapp.php74

After that you have to potentially update the app, in case those env variables are used. Generally all Cloudron injected env vars are now prefixed with CLOUDRON_ to avoid potential env var collisions.

[girish]

This is to do with the manifest changes in 7.1. Cloudron manifest v1 is not supported anymore in 7.1. The main change from manifest v1 to v2 is that env variables have the CLOUDRON_ prefix.

manifest v2 was added ~3 years ago in Cloudron 4.1