How should I handle configuration and secrets in MySQL?
Configuration must be available to the application without exposing credentials in source control, logs or browser code. What belongs in the runtime and which access controls matter?
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Configuration must be available to the application without exposing credentials in source control, logs or browser code. What belongs in the runtime and which access controls matter?
I'm running the latest build of the Docker Apple Silicon Preview. I created the tutorial container/images and it works fine. When I went to create a custom YAML file and run docker-compose I get the following error when pulling mysql: ERROR: no matching manifest for linux/arm64/v8 in the manifest list entries Here is a snippet from my YAMl file: version: '3'
I have a docker-compose file and a Dockerfile. MySQL is installed properly. I have set MYSQL_ROOT_PASSWORD . But when trying to access mysql db, getting the error - Access denied. I have read the other threads of this site, but couldn't get that much help. :( Here is my docker-compose file: version: '3' volumes: db_data: {} services: db: build: context: . do
New to development & self-teaching (thanks Covid) so this could be sloppy :( sorry... let me start off by saying I don't care about the data in the database - if it is easier to wipe it and start fresh, I'm good with that (don't know how to do that but I'm ok with it) Not sure what caused the issue but one day MySQL wouldn't start. Using service MySQL Re