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 If I recall correctly, don't quote me on this, that the APP_SECRET Is also used for 'remember me' tokens. So if it leaks, you can get into any account.
Which yeah.. It needs to be in .env.local instead at the very least.
@stefan Op zich wel begrijpelijk. In Duitsland verloopt het voetbal zonder grote problemen, en zitten supporters vaak door elkaar heen. Dat soort nette supporters wil je hier niet hebben. In zo'n geval kun je niet eens de ME inzetten. Dan is als burgemeester de lol er snel vanaf.
I'm gonna be very busy until the 10.06. with organizing a charity event & I'm visiting extended family in germany for one week - I won't find time to stream or do much else to generate income for an entire month, so y'all get 10% off on all items in my shop! boosts are appreciated! :thx:
Guys I need some helping hand. I need some good reading (book/article) on the proper way of writing OOP. I gave a project where we use classes, but they are more used as a package if functions then working like objects. Like a class of only statics, passing around IDs not the real objects of data (this sending SRP down the drain), arrays, generally functional programming with extra steps. I'd fancy even a discussion as I want to slowly explain all that to my teammates #php#oop#programming
TIA
@AmyIsCoolz From a dev: telegram promises encrypted messaging, but they have their own way of encrypting these messages and they've never been open enough so a third party could verify it.
