@Nicolas One way to avoid this mistake is use getenv('CLOUDRON_MYSQL_USERNAME'), getenv('CLOUDRON_MYSQL_DATABASE') instead of the raw values. This way when you migrate next time, it will pick up the correct database connection values.
@p44 The MySQL database in Cloudron is shared by all the apps. In MySQL 5.7.5+, they changed the behavior to have ONLY_FULL_GROUP_BY to be the default to be more compliant. Disabling this at the server level will cause issues for other apps.
I believe LAMP app supports cron, in that case use the following script to auto-pull from a git repo whenever an update is pushed to that repo:
Put in /app/data/updateGit
## CD to the path where the app is installed.
LOCAL=$(git rev-parse @)
REMOTE=$(git rev-parse "$UPSTREAM")
BASE=$(git merge-base @ "$UPSTREAM")
if [ $LOCAL = $REMOTE ]; then
elif [ $LOCAL = $BASE ]; then
echo "Need to pull"
elif [ $REMOTE = $BASE ]; then
echo "Need to push? Some files changed / commited here, this should not have happened."
echo "Diverged?? Help!"
Then in /app/data/crontab:
*/5 * * * * bash /app/data/updateGit 2>&1
## Or if you wanna avoid filling logs:
*/5 * * * * bash /app/data/updateGit 2>&1 > /dev/null
@mathieuepitech Apps on Cloudron send email with a specific email id and with a SMTP username/password. This is not just a security measure but also prevents misconfigured apps from sending emails with arbitrary domains resulting in your server being blacklisted as a spam bot.
The specific email id/mail from that the app will use is the in the app configure dialog. The SMTP credentials for sending email are available as environment variables. In PHP, you can simply use getenv('MAIL_SMTP_SERVER') etc instead of hardcoding the credentials.