@ramsey I always only did kubectl apply for changes, never delved deeper so I didn't know this option! I switched to Helm that handles revisions automatically for rollbacks too...
@rob this is the Docker snippet that I was talking you about to avoid needed the wait-for script. You define the healthcheck on the MySQL service in Docker Compose:
@willpower232@rob definitely! But it's just a small improvement over Rob's approach that he had in his slides at #phpday, where he was executing a well known "wait-for" script
After lunch, @OndrejMirtes snuck in the #phpday lighting talk session talk to us about @phpstan 1.11 new release, with a couple of interesting new features!
Why does #Symfony define what appears to be a “real” value for APP_SECRET in the .env file that’s committed to your repository, and then, right above it, there’s a comment that says (in all caps):
“DO NOT DEFINE PRODUCTION SECRETS IN THIS FILE NOR IN ANY OTHER COMMITTED FILES.”
Where’s the documentation that explains what APP_SECRET is used for? Why doesn't it put this value in .env.local (ignored by .gitignore)?
@ramsey@manal@nicolasgrekas well it's not sensible if it's used only locally, and then you use a .env.prod or (better) inject a real env variable in your prod environment.
I managed to avoid #Kubernetes for 10 years, but it’s finally caught up to me, so I hope I’m a Kubernetes god after going through all this required (by job) Kubernetes training.
@maxalmonte14@dantleech another useful use case of traits for me is splitting utility code inside PHPUnit tests, where you're already bound by the TestCase inheritance chain.
@afilina@dantleech@maxalmonte14 totally agree. And in fact your reply made me remember another use case for traits, exactly to avoid inheritance: a Timestampable trait with createdAt and updatedAt properties and getters to avoid to create an AbstractTimestampableEntity.