-
Notifications
You must be signed in to change notification settings - Fork 2.2k
Provide mechanism to extend mysql image with additional SQL init scripts #24
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
Comments
One problem here is that
We talked about using It would be nice to have extra SQL scripts on startup though. |
This will close both docker-library#18 and docker-library#24. The scripts are located in the /docker-entrypoint-initdb.d directory. Paired on this with @benkiefer
This would be really useful. |
It is not very usable without this feature. I have done as williamsdev in his PR for make it woking for me, but something from the official images should come, as it does in the postgres one. |
The changes we suggested in #53 should make this simpler to add, too, as the init sql is now just passed to the mysql client. |
+1 Actually, I did a similar thing as @williamsbdev in #31 |
+1 |
+1 |
1 similar comment
+1 |
This would be fairly simple to add with the new system for initializing the database used in #53. |
@ltangvald does that mean we're going to have a proper way to invoke instructions against |
+1 |
Please provide mechanism to extend this image by providing additional SQL scripts to be executed upon initial server startup.
See official postgres image for example on how this can be done (“How to extend this image” section in readme).
You can arrange special directory for SQL files. All
*.sql
files found in that directory shall be appended to$TEMP_FILE
that will be passed as--init-file
parameter to MySQL.The text was updated successfully, but these errors were encountered: