@msbt the old LAMP app will be left as-is. So, no change to that in the foreseeable future.

apt install -y cron apache2-dev php7.4 php7.4-{bcmath,bz2,cgi,cli,common,curl,dba,dev,enchant,fpm,gd,gmp,imap,interbase,intl,json,ldap,mbstring,mysql,odbc,opcache,pgsql,phpdbg,pspell,readline,soap,sqlite3,sybase,tidy,xml,xmlrpc,xsl,zip} libapache2-mod-php7.4 php-{apcu,date,geoip,gettext,imagick,gnupg,mailparse,pear,redis,twig,uuid,validate,zmq} ghostscript libgs-dev ffmpeg && \

is what we install. exiftool is there in the base image.

@saikarthik said in IMAP port and server settings for LAMP app mail client:

What I blurred out in the picture is actually a valid cloudron mailbox ID.

Yes, but it seems there is some extra text before it like Test User: "Test User". Can you remove that and try?

hi @girish . great info, thanks. I will try it out.

@girish you're a genius man! I think it should work, I'll try it and come back. Thanks!!

@girish Thanks! I was hoping to get an official feature going - but thanks, I'll check the link out!

@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.

The full env list for MySQL is at https://cloudron.io/documentation/custom-apps/addons/#mysql

@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.

The correct way to fix this is to have the app disable this mode at a session level. Like https://dev.mysql.com/doc/refman/5.7/en/group-by-handling.html . Essentially, the app has to call "SET GLOBAL sql_mode=(SELECT REPLACE(@@sql_mode,'ONLY_FULL_GROUP_BY',''));" after creating a connection.

So, I guess the answer is:

Either sendy has to provide a mechanism to do the above. Alternately, you cannot run sendy in Cloudron. You have to create a dedicated server for this and setup MySQL accordingly.

I put a package at https://git.cloudron.io/cloudron/php7.3-postgres-app/ . This is a PHP 7.3 app that has postgres.

@Trankery Yup, I will mark this as a feature request for a future release.

@girish & @jdelon02

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

#!/bin/sh ## CD to the path where the app is installed. cd /app/data/public UPSTREAM=${1:-'@{u}'} LOCAL=$(git rev-parse @) REMOTE=$(git rev-parse "$UPSTREAM") BASE=$(git merge-base @ "$UPSTREAM") if [ $LOCAL = $REMOTE ]; then echo "Up-to-date" elif [ $LOCAL = $BASE ]; then echo "Need to pull" git pull elif [ $REMOTE = $BASE ]; then echo "Need to push? Some files changed / commited here, this should not have happened." else echo "Diverged?? Help!" fi

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

This will check if a pull is needed from a repo every 5 minutes. (Re: https://crontab.guru/every-5-minutes)

You can also modify the bash script to rebuild, npm install, composer install, etc when needed too.

@girish sorry for spamming this old thread. I added a complete new post: https://forum.cloudron.io/topic/4203/git-push-ci-cd-workflow-for-the-lamp-app

@hdavy2002 Pushed an update to fix this now.

Okay, I understand. It's fine by me.

The separate admin panel's latest release just renders a blank page for me (locally and on LAMP) ¯_(ツ)_/¯

@jeau It looks like I closed https://git.cloudron.io/cloudron/lamp-app/issues/14 by mistake and this went off our radar. I have reopened it.

@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.

@jensbee4 If you click on the logs button in the app icon in the dashboard, you will see the access logs. We log in the combined format - "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-agent}i\"". More information about the format is http://httpd.apache.org/docs/current/mod/mod_log_config.html#customlog

@murgero I added it after you asked the question 🙂

@jepster We have pushed an update that should make it simpler now. Also updated the docs - https://cloudron.io/documentation/apps/lamp/#running-composer

Let's discuss this in https://forum.cloudron.io/topic/1700/lamp-stack-composer-cannot-require-any-package-cannot-write-into-cache

A bunch of mods are already installed, but not activated.

I would separate this into:

Activating already installed mods Installing and activating new monds

Would be great if you could update this thread with your findings. Also please note that the memory settings for the addons are currently not preserved across app restores or even server reboots. We are working on this fix and you can see the status of it at https://git.cloudron.io/cloudron/box/issues/566