Closed stevecomrie closed 1 year ago
The code responsible for processing .sql and .sql.gz files mounted to /docker-entrypoint-initdb.d does not work.
.sql
.sql.gz
/docker-entrypoint-initdb.d
This PR fixes that process with these steps during the DB init phase of run.sh
run.sh
$MYSQL_DATABASE
$MYSQL_USER
mysqld
Currently open issues that will be resolved by this PR:
https://github.com/yobasystems/alpine-mariadb/issues/63
The update is identical for all 3 target image architectures.
The code responsible for processing
.sql
and.sql.gz
files mounted to/docker-entrypoint-initdb.d
does not work.This PR fixes that process with these steps during the DB init phase of
run.sh
$MYSQL_DATABASE
and$MYSQL_USER
have been created and granted privileges./docker-entrypoint-initdb.d
to see if there are any files worth processing.mysqld
server temporarily to process the seed files.sql
files: Directly push the contents into$MYSQL_DATABASE
via the mysql client CLI.sql.gz
files: Gunzip and pipe the direct output into$MYSQL_DATABASE
via the mysql client CLICurrently open issues that will be resolved by this PR:
https://github.com/yobasystems/alpine-mariadb/issues/63
The update is identical for all 3 target image architectures.