Symfony Station covers the essential news in the Symfony, PHP, Cybersecurity, and Fediverse development communities with a focus on protecting democracy. Please make a small donation to help cover our out-of-pocket costs. Our labor is provided free of charge to support the communities we write about. #symfony#drupal#PHP#cybersecurity#fediverse
Symfony Station covers the essential news in the Symfony, PHP, Cybersecurity, and Fediverse development communities with a focus on protecting democracy. Please make a small donation to help cover our out-of-pocket costs. Our labor is provided free of charge to support the communities we write about.
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)?
SymfonyOnline June 2024: Announcement of workshops topics! (Symfony Blog) (symfony.com)
Check out the schedule of workshops and register
New in Symfony 7.1: New Dependency Injection Attributes (Symfony Blog) (symfony.com)
Symfony 7.1 adds two new Dependency Injection attributes to allow autowiring specific methods as callables and defining services inside PHP classes.
New in Symfony 7.1: Improved Access Token Authenticator (Symfony Blog) (symfony.com)
Symfony 7.1 enhances its Access Token Authenticator by adding RSA signature support and introducing a new CAS 2.0 token handler.