In summary:
If you have a standard 19.1 package installation and have not disabled the automatic update, the container should be updated automatically.
Did that work for you?
OK, so ignore the ues-epl.sh for I am only using the community edition without colabra and chat.
However, I still have a problem. the egroupware-docker-install.log file has been over written with
Fix APC(u) configuration, set apc.shm_size=128M in /etc/php/7.3/cli/conf.d/20-apcu.ini
EGroupware successful updated
Fix APC(u) configuration, set apc.shm_size=128M in /etc/php/7.3/cli/conf.d/20-apcu.ini
EGroupware successful updated
EGroupware successful updated
EGroupware successful updated
EGroupware successful updated
Fix APC(u) configuration, set apc.shm_size=128M in /etc/php/7.3/cli/conf.d/20-apcu.ini
EGroupware successful updated
Fix APC(u) configuration, set apc.shm_size=128M in /etc/php/7.3/cli/conf.d/20-apcu.ini
EGroupware successful updated
Fix APC(u) configuration, set apc.shm_size=128M in /etc/php/7.3/cli/conf.d/20-apcu.ini
EGroupware successful updated
Fix APC(u) configuration, set apc.shm_size=128M in /etc/php/7.3/cli/conf.d/20-apcu.ini
EGroupware successful updated
Fix APC(u) configuration, set apc.shm_size=128M in /etc/php/7.3/cli/conf.d/20-apcu.ini
EGroupware successful updated
Fix APC(u) configuration, set apc.shm_size=128M in /etc/php/7.3/cli/conf.d/20-apcu.ini
EGroupware successful updated
EGroupware successful updated
Fix APC(u) configuration, set apc.shm_size=128M in /etc/php/7.3/cli/conf.d/20-apcu.ini
EGroupware successful updated
EGroupware successful updated
Fix APC(u) configuration, set apc.shm_size=128M in /etc/php/7.3/cli/conf.d/20-apcu.ini
EGroupware successful updated
Fix APC(u) configuration, set apc.shm_size=128M in /etc/php/7.3/cli/conf.d/20-apcu.ini
EGroupware successful updated
EGroupware successful updated
EGroupware successful updated
EGroupware successful updated
EGroupware successful updated
EGroupware successful updated
Fix APC(u) configuration, set apc.shm_size=128M in /etc/php/7.3/cli/conf.d/20-apcu.ini
EGroupware successful updated
EGroupware successful updated
So I imagine the automatic docker update is working but I have no idea when the updates happened and only some give a reason for the the update. But, silly me, I thought those passwords generated by the v19 update were going to stay in the log file, but no, they have been over written by the docker updates.
Now I have the problem that apparently sysop in the egroupware user list is not sysop in the header login page. I changed sysop’s password in the admin app’s user list but the new password does not work in the egroupware/setup page. I must get access to these pages to get SMTP to work in the docker container. So:
What user in the admin app’s user list is allowed to login in the upper box of the setup page?
If no user in the admin’s apps user list is allowed into setup how do I recover the users and the passwords that were over written?
ABOVE IS FIXED I found the old login credentials from my original install and the header.inc.php is intact and I got to the setup page. Check installation yields all green check marks. But I am not getting emails when an event comes due. I get the notice within the egoupware web page, but no email.
I am reading the SMTP-only mail account for notifications readme page and am stumped with the instructions:
Simply use what wizard where? I cannot find any selection in the admin menu that yields the panel with the admin-mailaccount: admin-mailaccount title. I added the SNMP to the sysop account and I am not getting mails.
First:
please create a separate topic for each problem.
Never edit the contents of your topic in this way. Nobody will notice this and it will not be sent by e-mail.
Hmmmm…
I can’t imagine. It is always only attached at the end of the file… In my Installation the access data from the first installation are at the top of the file.