Docker compose script fails to setup database tables/schemas

[Technifocal]

After a lot of failures (:cry:) I've concluded that the docker-compose script does not actually setup a operational Dojo stack.

1_db.sql.tpl gets copied to 1_db.sql here and then is never used again. This means that the database is at no point initialized and thus the entity of Dojo doesn't work (Oops, guess I'm the first non-dev user! 👀).

I assume this code should also contain another block above that is roughly:

if [ -f /docker-entrypoint-initdb.d/1_db.sql ]; then
  mysql -h"db" -u"root" -p"$MYSQL_ROOT_PASSWORD" "$MYSQL_DATABASE" < /docker-entrypoint-initdb.d/1_db.sql
  echo "Updated database with 1_db.sql"
fi

[kenshin-samourai]

database initialization during first install of dojo is a 3 steps process:
1/ 1_db.sql.tpl gets copied to 1_db.sql (here)
2/ 1_db.sql gets copied into the /docker-entrypoint-initdb.d directory of the mysql container (here)
3/ 1_db.sql is executed (here)

the last step is a feature provided by the mysql docker image (see section "Initializing a fresh instance" of this page)

this process has been tested by non-dev users. it's likely that your "failures" have another cause.

[Technifocal]

I'm beyond stupid. I completely forgot I swapped mysql to mariadb. Sorry for wasting your time.

[kenshin-samourai]

no problem