### MySQL ################################################
mysql:
build:
context: ./mysql
args:
- MYSQL_VERSION=${MYSQL_VERSION}
environment:
- MYSQL_DATABASE=${MYSQL_DATABASE}
- MYSQL_USER=${MYSQL_USER}
- MYSQL_PASSWORD=${MYSQL_PASSWORD}
- MYSQL_ROOT_PASSWORD=${MYSQL_ROOT_PASSWORD}
- TZ=${WORKSPACE_TIMEZONE}
volumes:
- ${DATA_PATH_HOST}/mysql:/var/lib/mysql
- ${MYSQL_ENTRYPOINT_INITDB}:/docker-entrypoint-initdb.d
ports:
- "${MYSQL_PORT}:3306"
networks:
- backend
That volumes section is taking the DATA_PATH_HOST in the .env file and telling the docker container to pass through all the data in /var/lib/mysql to the DATA_PATH_HOST/myqsl folder.
So if you bring your container down and then bring it back up OR bring up another MySQL container that points to that, you will be all set.
Let me just get the last part straight
${DATA_PATH_HOST}/mysql:/var/lib/mysql
${DATA_PATH_HOST} is a variable for getting the string DATA_PATH_HOST.
is the part after
: a docker tag?
So in this case, it is tying C:\users\{{your_username}}\.laradock\data\mysql to the directory /var/lib/mysql in the mysql docker container.
And the
/var/lib/mysql is where it is in the container?
Man, you're amazing. Thanks again! :)
I'm going to go try all this out
So basically it's creating a shared space that the container and host can both write to. It's actually also doing this for your laravel app as well. When you enter docker-compose exec workspace bash, you are seeing those files from the container side which stores them in /var/www.
We changed the location of that in the env file when we modified APP_CODE_PATH_HOST
Anytime! I am going to sign off for tonight, but I will be around. :)
Hi everyone I’m having problem with the php-worker.
What i tried to do is merging multiple pdf into one single pdf.
Here is the library I used to do a pdf merging : lara-pdf-merger
I saw on the php-worker Dockerfile that the worker is using php alpine. But i can also enable the GD library through the env, set the INSTALL_GD to true referring to #2516 , but instead of merging it what i got is a blank pdf and also it changed my source pdf to a blank page as well.
But if i run the queue manually through the workspace it works well.
If there is some Laradock-specific documentation -- other than the extant docs -- I'd greatly appreciate it.
Hi there, CODEIGNITER is mentioned in Laradock documents but it doesn't exist as expected: https://laradock.io/documentation/#install-codeigniter does anyone know about it please?
I was expecting to see that within the following file https://github.com/laradock/laradock/blob/master/docker-compose.yml from revision
6b16f2b
@toomaj_gitlab try to set the codeigniter app as a default/normal PHP application using the
nginx\sites\app.conf.example in the Nginx instead of nginx\sites\laravel.conf.example
Quick question re:
redis-cluster . It works fine in Laravel (yay!). However when I connect to the container via docker-compose exec redis-cluster bash, it connects fine, but when I try to run redis-cli it says Could not connect to Redis at 127.0.0.1:6379: Connection refused. Which is strange!
When I try to push with code pipeline, it gives error and not working. what should I do?
@tcagkansokmen As far as I can tell, elastic beanstalk doesn't support docker-compose which is what Laradock uses. You will have to create an EB custom json file following their format.