We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Duplicate of https://github.com/m1k1o/blog/issues/28
https://github.com/m1k1o/blog/issues/28
Config:
version: "3" services: webserver: image: m1k1o/blog:latest container_name: blog_apache environment: TZ: Europe/Moscow BLOG_DB_CONNECTION: mysql BLOG_MYSQL_HOST: mariadb BLOG_MYSQL_PORT: 3306 BLOG_MYSQL_USER: blog BLOG_MYSQL_PASS: blog # use secure password BLOG_DB_NAME: blog restart: unless-stopped ports: - 9999:80 volumes: - ${DATA-./data}:/var/www/html/data mariadb: image: mariadb:10.1 container_name: blog_mariadb environment: MYSQL_USER: blog MYSQL_PASSWORD: blog # use secure password MYSQL_DATABASE: blog MYSQL_ROOT_PASSWORD: root # use secure password restart: unless-stopped volumes: - mariadb:/var/lib/mysql - ./app/db/mysql:/docker-entrypoint-initdb.d:ro volumes: mariadb:
The text was updated successfully, but these errors were encountered:
Do you have ./app/db/mysql directory available? There must be schema that is automatically created. This file must be in there: https://github.com/m1k1o/blog/tree/master/app/db/mysql
./app/db/mysql
Sorry, something went wrong.
No, fixed it: sudo chmod 777 app/db/mysql/ cd app/db/mysql/ && wget https://raw.githubusercontent.com/m1k1o/blog/master/app/db/mysql/01_schema.sql
sudo chmod 777 app/db/mysql/
cd app/db/mysql/ && wget https://raw.githubusercontent.com/m1k1o/blog/master/app/db/mysql/01_schema.sql
Then... The same problem.
You need to remove the mariadb volume and start again so that it performs the initialization.
# this removes volumes docker-compose down -v
It worked.
No branches or pull requests
Duplicate of
https://github.com/m1k1o/blog/issues/28
Config:
The text was updated successfully, but these errors were encountered: