No 'homestead' MySQL user?

Question

No 'homestead' MySQL user?

Closed this issue 9 years ago · 15 comments

@ibourgeois any particular reason why the lines to create the homestead user and database for MySQL are commented out? Without this we can't find any way to enter values in Laravel's config that will successfully connect the app to the database.

https://github.com/laraedit/laraedit-docker/blob/master/src/scripts/mysql.sh#L18-L23

Thanks.

Answer 1 · 2016-03-04T01:57:01.000Z

those scripts aren't being used in the docker container, they are only there as a reference of what I still need to implement from homestead.

the default user is root and the password is secret.

I can add a homestead user if you'd like though!

Answer 2 · 2016-03-04T05:26:21.000Z

Thanks for the response. We tried setting the .env values as:

DB_USERNAME=root
DB_PASSWORD=secret

and still Laravel erred with Access denied for user 'root'@'localhost'. Only by creating the user ourselves and granting it access did the connection work. What are we missing?

Answer 3 · 2016-03-04T05:46:55.000Z

testing that now.

Answer 4 · 2016-03-04T06:05:04.000Z

i wasn't able to replicate this. did you create the database first?

if so, are you able to share the logs?

Answer 5 · 2016-03-04T06:12:21.000Z

by default, there is no preexisting database in this container. you'll need to create one.

.env file should include:

DB_HOST=127.0.0.1
DB_PORT=3306
DB_DATABASE=your_db_name
DB_USERNAME=root
DB_PASSWORD=secret

Answer 6 · 2016-03-04T16:18:51.000Z

it makes sense to create the mysql user "homestead" with password "secret" and database "homestead". This way the container is ready to go when we type "laravel new xxxxxx".
like in the homestead vagrant box

Answer 7 · 2016-03-07T02:44:59.000Z

agreed. now that I am home, I will work on this first thing in the morning. thanks for the suggestion!

Answer 8 · 2016-03-08T14:43:21.000Z

same problem as @waldemarfm i had to create a new user myself. if not, i get Access denied for user 'root'@'localhost'

Answer 9 · 2016-03-08T16:12:31.000Z

were you using something like the mysql workbench to access the database?

the reason i ask is because I was unable to trigger any access is denied errors from laravel or from within the container itself. however, i did get access denied when trying to connect with the workbench.

I was able to correct this issue by running the following command:
GRANT ALL PRIVILEGES ON *.* TO 'root'@'%' IDENTIFIED BY 'secret';

and restarting the mysql service

I have updated this on the dev branch, and if it works, i will push it to master as well.

Answer 10 · 2016-03-08T17:16:01.000Z

@ibourgeois i just tested again with a fresh container, same problem.
here is a picture to show you (sorry, i cannot copy paste with my terminal):

Answer 11 · 2016-03-08T18:10:53.000Z

did you start this container from the command line or with kitematic?

Answer 12 · 2016-03-08T18:13:46.000Z

none, i am running a thing like kitematic, but on my server: https://www.synology.com/en-us/dsm/app_packages/Docker

Answer 13 · 2016-03-08T18:21:35.000Z

try using no password

Answer 14 · 2016-03-08T18:27:57.000Z

changed my .env and remove password for mysql user root: same error message "access denied for ...".
I'll wait for your new version, with the user already created in the image.
Please make a user homestead, not just root user.

Answer 15 · 2016-03-09T02:23:17.000Z

i just committed a pull request that creates a homestead user with a password of secret as well as creates the homestead database.

if you allow about 30 minutes to build on the docker hub: https://hub.docker.com/r/laraedit/laraedit/builds/bxwxunhfpeesitqtpkcvdb8/

it should then be available to pull in using docker, kitematic, etc...