Explore the evolution of web analytics and the impact of privacy laws like GDPR on data collection strategies. Learn from industry expert Alexander Veit at T3CON23.
Explore Symfony's AssetMapper & UX for minimal JS with Kévin Dunglas. For complex needs like hardware-intensive or mobile apps, API-based JS is crucial. Learn when to use Symfony UX vs. API Platform'...
Today's Payload newsletter is out with the latest Symfony, Drupal, PHP, Cybersecurity, and Fediverse news. If you like what you see please join our list or even make a small donation to help cover our fixed costs. Thanks for reading! #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. #symfony#drupal#PHP#cybersecurity#fediverse
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)?