Need v19 upgrade details

[smaugain]

Hi,
I try to upgrade my v17 installation to v19 but the Egroupware docker don’t start correctly.
I need to have more details on the way docker get the login and password of Mysql database. Before, php script was getting the user and password in the header.inc.php.
But now how does it works ?
Does docker read the old header.in.php in /var/lib/egroupware ?
There’s an new file docker-compose.yml who seems to have database parameters. Do I need to edit him ? There are some commented lines but some starts with a « - » character, why ?
Thanks
Silvère Maugain

[StefanU]

Hi Silvère,

Please describe your installation. At least once which OS you are using…

but the Egroupware docker don’t start correctly.

What says docker ps?
Did you check the installation log?:
/var/lib/egroupware/egroupware-docker-install.log

Regards
Stefan

[smaugain]

After several tries, I successfully migrated my Egroupware v17 installation from the Debian packages to the 19 docker version.

Particularities of my installation in version 17:

• Debian Buster 10.1.
• Apache web server.
• Local Mysql base.
• Authentication by LDAP.
• LDAP address book.
• SQLFS on an other partition than “/ var”.
• Backup directory “backup” on an other partition than “/ var”.

Problems :

• Disk space: The Egroupware-docker package is enough for a basic installation, no need for rocket or collabora much bigger. Bear in mind that “/var/lib/docker” will do almost 2GiB with only Egroupware-docker.
• Header.inc.php: Probable file loss when purging old v17 packages. The installation was attempting to run on a file provided by default by the package. Restore the old file in /var/lib/egroupware/.
• Mysql: No remote connection privileges for the egroupware user of the database. Added GRANT “172.%” to allow the container to connect to the host database.
• docker-compose.yml: Edit file to complete the parameters “EGW_DB_NAME” “EGW_DB_USER” “EGW_DB_PASS”.
• LDAP: No connection to the LDAP database on the host. Using an SQL editor to modify the “egw_config” table. Fields “ldap_contact_host” and “ldap_host” to 172.17.0.1.
• SQLFS: Previous use of a different path for storing files. Moving the contents of the “files” and “backup” folders into “/var/lib/egroupware/default/”. Using an SQL editor to modify the “egw_config” table. Fields “backup_dir” to “/var/lib/egroupware/default/backup/” and “files_dir” to “/var/lib/egroupware/default/ files”.
• docker-compose: You have to use “docker-compose restart egroupware” to restart Egroupware and take into account these parameters.

To-do :

• Find how to allow “Follow Symlink” in nginx server to move SQL files in an other partition.

[RalfBecker]

Find how to allow “Follow Symlink” in nginx server to move SQL files in an other partition.

Symlink wont work, as /var/lib/egroupware is bind-mounted into EGroupware and Nginx containers.
So you have two possibilites:
a) Change the bin-mount / volume in the docker-compose file to the mount-point of your disk
b) Change the mount-point of your disk to /var/lib/egroupware

I strongly recommend b) as modifying the docker-compose file makes it harder for you on the long run, when we update it again eg. to add further containers.

Ralf

[smaugain]

I did not think about this solution, I will create a new mount-point.
Thanks
Silvère