Submission for egroupware core setup

[sneaky]

Hello Ralf and other core-developers,

during my manual egroupware installation for my dockerfile, I stumbled
over 2 strange points:

1. installation step “input information for header.inc.php”

The default database port is always 3306, the default server is always
"localhost"- but if You link the container with a mysql container, the
data is already stored in environment variables. I updated the file
setup/inc/class.setup.header.inc.php in a way that it works “the normal
way” and “the manual docker container installation way”.

2. installation step 2 (configuration)

it looks for folders named ‘/var/lib//default/files’ and
’/var/lib//default/backup’ - it seems the variable $egroupwareDirName
was not set before line 247 in file
setup/inc/class.setup_process.inc.php , so I added a default value
’egroupware’

Both files are attached to this email.

I don’t know if You maybe can add my submission to egroupware core or
maybe there’s another solution for those points.

sneaky(x) alias

André Scholz

[Ralf_Becker_Stylite]

Hi Andre,

Hello Ralf and other core-developers,

during my manual egroupware installation for my dockerfile, I stumbled
over 2 strange points:

1. installation step “input information for header.inc.php”

The default database port is always 3306, the default server is always
"localhost"- but if You link the container with a mysql container, the
data is already stored in environment variables. I updated the file
setup/inc/class.setup.header.inc.php in a way that it works “the
normal way” and “the manual docker container installation way”.

EGroupware is already prepared to install in docker and understand
linking via environment variables: doc/rpm-build/post_install.php allows
to set arbitrary values and for the database we can fetch environment
variables on run-time by using their name prefix with an “@”. That even
works if you reconfigure the container linkage.

So when your container starts you call:

doc/rpm-build/post_install.php
–db_host @MYSQL_PORT_3306_TCP_ADDR
–db_port @MYSQL_PORT_3306_TCP_PORT
–db_name @MYSQL_ENV_MYSQL_DATABASE
–db_user @MYSQL_ENV_MYSQL_USER
–db_pass @MYSQL_ENV_PASSWORD
–data_dir /var/lib/egroupware # is the default anyway

doc/rpm-build/post_install.php --help gives all available options.

post_install.php detects if EGroupware is installed and then only checks
if an update is necessary.

Ralf

2. installation step 2 (configuration)

it looks for folders named ‘/var/lib//default/files’ and
’/var/lib//default/backup’ - it seems the variable $egroupwareDirName
was not set before line 247 in file
setup/inc/class.setup_process.inc.php , so I added a default value
’egroupware’

Both files are attached to this email.

I don’t know if You maybe can add my submission to egroupware core or
maybe there’s another solution for those points.

sneaky(x) alias

André Scholz

–
Ralf Becker
Director Software Development

Stylite AG

Isaac-Fulda-Allee 9 | Tel. +49 6131 32702-0
D-55124 Mainz | Fax. +49 6131 32702-70

Email: rb@stylite.de

www.stylite.de | www.egroupware.org

Managing Directors: Andre Keller | Gudrun Mueller
Chairman of the supervisory board: Prof. Dr. Birger Leon Kropshofer

VAT DE214280951 | Registered HRB 46224 Mainz Germany

[sneaky]

Hi Ralf,

it seems, it doesn’t work with exitsting databases if I don’t provide
all the information…

/usr/local/bin/php -d memory_limit=-1
/var/www/html/egroupware/setup/setup-cli.php --setup-cmd-database
sub_command=create_db ‘domain=default’ ‘db_type=mysqli’
‘db_host=@MYSQL_PORT_3306_TCP_ADDR’ ‘db_port=@MYSQL_PORT_3306_TCP_PORT’
‘db_name=egroupware’ ‘db_user=egroupware’ ‘db_pass=xyz’ ‘db_root=root’
‘db_root_pw=’ 'db_grant_host=localhost’
Can not connect to mysqli database mysql on host
@MYSQL_PORT_3306_TCP_ADDR:@MYSQL_PORT_3306_TCP_PORT using user root!
(ADOdb::Connect(172.17.0.2:3306, root, $Password, mysql) failed.)

Following problem: If the database already exists, You can’t change the
database password by using MYSQL_ENV_PASSWORD, because the mysql docker
doc says:
"Usage against an existing database

If you start your mysql container instance with a data directory that
already contains a database (specifically, a mysql subdirectory), the
$MYSQL_ROOT_PASSWORD variable should be omitted from the run command
line; it will in any case be ignored, and the pre-existing database will
not be changed in any way."
So this means, the database isn’T chaned in any way, not even the user
table isn’t touched.
So this can only work in case that the passed variable is the same
already stored in database, can’t it?
I think I can’t use it to update my container’s information.
But I try to use it for new installations.

Thanks for that info.

André alias sneaky(x)