- Fixing MariaDB issues after rebuilding the container
- docker-compose does not recognize variables from
.env
file - Windows Based Installation
For any reason after rebuilding the container if you are not be able to access MariaDB correctly with the previous configuration. Follow these instructions.
The parameter 'db_name'@'%'
needs to be set in MariaDB and permission to the site database suitably assigned to the user.
This step has to be repeated for all sites available under the current bench.
Example shows the queries to be executed for site localhost
Open sites/localhost/site_config.json:
code sites/localhost/site_config.json
and take note of the parameters db_name
and db_password
.
Enter MariaDB Interactive shell:
mysql -uroot -p123 -hmariadb
Execute following queries replacing db_name
and db_password
with the values found in site_config.json.
UPDATE mysql.user SET Host = '%' where User = 'db_name'; FLUSH PRIVILEGES;
SET PASSWORD FOR 'db_name'@'%' = PASSWORD('db_password'); FLUSH PRIVILEGES;
GRANT ALL PRIVILEGES ON `db_name`.* TO 'db_name'@'%'; FLUSH PRIVILEGES;
EXIT;
Note: For MariaDB 10.4 and above use mysql.global_priv
instead of mysql.user
.
If you are using old version of docker-compose
the .env file needs to be located in directory from where the docker-compose command is executed. There may also be difference in official docker-compose
and the one packaged by distro. Use --env-file=.env
if available to explicitly specify the path to file.
- Set environment variable
COMPOSE_CONVERT_WINDOWS_PATHS
e.g.set COMPOSE_CONVERT_WINDOWS_PATHS=1
- While using docker machine, port-forward the ports of VM to ports of host machine. (ports 8080/8000/9000)
- Name all the sites ending with
.localhost
. and access it via browser locally. e.g.http://site1.localhost
- If you have made changes and just want to start over again (abandoning all changes), remove all docker
- containers
- images
- volumes
- Install a fresh