Skip to content
New issue

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

Update docker-compose.yml #112

Merged
merged 2 commits into from
Dec 2, 2019
Merged

Update docker-compose.yml #112

merged 2 commits into from
Dec 2, 2019

Conversation

morpheus7CS
Copy link
Contributor

Hi @fideloper,

I have just started using Vessel today and upon running ./vessel start MySQL container immediately exited with status Exit (1). It took me some time to find the issue in the first place as well as coming up with the right syntax.

I have added a commented out line for MYSQL_ALLOW_EMPTY_PASSWORD: 'yes' to the default docker-compose.yml file. As Laravel uses this by default on a new .env file, I thought it useful for newcomers and gives them the solution right there.

Furthermore, as you have referenced this as an issue a while back, I'm willing to lend a hand with the documentation, if you find you need any help. If you merge this option, I can update the docs accordingly. Let me know.

Kind regards,
g

@fideloper
Copy link
Contributor

Thanks for letting me know, I didn't catch that laravel's default is to have an empty password now!

@fideloper
Copy link
Contributor

I wonder if we want to have this line NOT commented out so it takes effect. In theory that shouldn't break it if the password is NOT empty?

@morpheus7CS
Copy link
Contributor Author

Hey, true. But the question I had was: would a new user try to actually deploy using this file, therefore possibly opening up the production DB to the World?

This is why I have commented it out, but maybe it makes sense to actually have it uncommented.

@fideloper
Copy link
Contributor

fideloper commented Jul 5, 2019 via email

@fideloper
Copy link
Contributor

Sorry I lost track of this, I went and had a baby and that's a bit distracting :D

If you want, can you add that line but keep it uncommented? I think that'll work best in terms of not being a surprise for Vessel users going forward.

@morpheus7CS
Copy link
Contributor Author

Sure, give me 5 minutes.

P.S. Totally understand the baby situation, have been there myself a few years back. ;)

@fideloper fideloper merged commit d178969 into shipping-docker:master Dec 2, 2019
@fideloper
Copy link
Contributor

Thanks!!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants