Content negotiation lets you serve HTML to browsers and JSON to apps from the same endpoint, without maintaining a separate API. Examples in Symfony, Laravel and Temma.

https://dev.to/amaury_bouchard/your-php-website-is-a-free-api-how-to-unlock-it-with-content-negotiation-2h0p
#php #webdev #api #temma

dev.to

Amaury Bouchard @amaury@phpc.social

· 6mo ago

Votre site web est déjà une API. Il suffit de renvoyer du JSON au lieu du HTML quand le client le demande. Même URL, même code métier. Je montre comment faire en Symfony, Laravel et Temma.

https://www.geek-directeur-technique.com/2026/04/04/content-negociation-en-php-votre-site-web-est-une-api-sans-le-savoir-exemples-symfony-laravel-et-temma
#PHP #API #WebDev #AFUPDay

geek-directeur-technique.com

Amaury Bouchard @amaury@phpc.social

· 6mo ago

Calling OpenAI from a PHP framework the same way you query a database

https://dev.to/amaury_bouchard/calling-openai-from-a-php-framework-the-same-way-you-query-a-database-4n8b
#php #openai #webdev #temma #temmaframework

dev.to

Amaury Bouchard @amaury@phpc.social

· 6mo ago

Protéger son app PHP contre les attaques CSRF sans jetons partout, c'est possible.

3 techniques combinées (Referer, POST only, SameSite=Lax), comparées en PHP pur, Laravel, Symfony et Temma.

https://www.geek-directeur-technique.com/2026/03/18/csrf-temma-vs-laravel-vs-symfony

#PHP #Security #CSRF #laravel #symfony #temma

geek-directeur-technique.com

Amaury Bouchard @amaury@phpc.social

· 10mo ago

@sysedit@mastodon.social @laravista@mastodon.uno No "sacred vs evil". Quite the opposite, actually. It’s not about polarizing practices, it’s about recognizing there’s no such thing as an absolute best practice. What works for a company with 800 developers rarely applies directly to a 3-person startup.
For sure, OOP is great, that’s not the point. But when it’s misused, with so many layers of indirection that you can’t follow the execution flow, it becomes a nightmare (like any practice when misapplied).