docker-php-tutorial VS berglas

I've started a series of tutorials on "Docker for PHP developers" some years ago and add new articles when I find the time. Each part "evolves" the codebase that I provide as a practical "working" example available at https://github.com/paslandau/docker-php-tutorial.

Docker is imho the way to go. Only downside for me is the file system performance on Mac and Windows compared to Linux. I've documented "our" setup in https://www.pascallandau.com/blog/docker-from-scratch-for-php-applications-in-2022/ which is part of a multi-part tutorial on "all things docker" for PHP devs => https://github.com/paslandau/docker-php-tutorial

All code samples are publicly available in my Docker PHP Tutorial repository on github. You find the branch with the final result of this tutorial at part-6-git-secret-encrypt-repository-docker.

In the latest part of my tutorial series on Docker for PHP developers I'm showcasing a setup for running Laravel on Docker: https://www.pascallandau.com/blog/run-laravel-9-docker-in-2022/

Deep and straight compose setup: https://github.com/paslandau/docker-php-tutorial there is a related series of blog posts somewhere.

Secret Manager: secure storage for sensitive data e.g passwords.

Google Secret Manager

API keys are easy to "leak" or compromise, so best to not only use the restrictions presented to you when you create them but physically protect them as well. Don't code them in plain-text, don't check them into GitHub, etc. Store them in a secure database or use a service like GCP Secret Manager.

I've been looking at Google Secret Manager which sounds promising but I've not been able to find any examples or tutorials that help with the actual practical details of best practice or getting this working. I'm currently reading about Cloud Functions which also sound promising but again, I'm just going deeper and deeper into GCP without feeling like I'm gaining any useful insights.

In this post, I described how to build secure GitHub Actions workflows by pull_request_target event instead of pull_request event. Using pull_request_target, you can prevent malicious codes from being executed in CI. And by managing secrets in secrets management services such as AWS Secrets Manager and Google Secret Manager and access them via OIDC, you can restrict the access to secrets securely. To migrate pull_request to pull_request_target, several modifications are needed. And pull_request_target has a drawback that it's difficult to test changes of workflows, so it's good to introduce pull_request_target to repositories that require strong permissions in CI. For example, a Terraform Monorepo tends to require strong permissions for CI, so it's good to introduce pull_request_target to it.

If you want to make these secrets more secure and get versioning and access logs for them, you may want to switch to Secret Manager later on. They can still be exposed as environment variables to your code. It's a little more setup work, so start with the simple approach at the top.

https://cloud.google.com/secret-manager https://aws.amazon.com/secrets-manager/