Here at MyBuilder we recently had the chance to work on a green-field project, which of course meant we were able to play with all the shiny new toys we’ve been dying to try out for a while.
We needed to extract a standalone PDF generation service from some work we’d already done in another project. It was a perfect candidate for running inside AWS Lambda, and thus also finally giving Bref a try in production.
I remember a colleague in a previous job repeating the mantra “program to interfaces, not implementations”.
This sounded like good advice, but it felt a little abstract to me, since in PHP variables do not have types. The values of the variables have types, but the type of an object in memory is never an interface — it’s always a class.
One of our front-end engineers, Sebastian, has been working on a few side projects recently, one of which included setting up user pools in AWS Cognito to handle his user management. As he was showing me around the things he’d been doing, it got me thinking “how easy would it be to defer Symfony’s authentication to Cognito as well?”.
It seems as if React is everywhere - follow this tutorial to uncover the power of React and at the very least have a production ready webform.
Our very own Neal Brooks has recently presented at SymfonyLive London 2018, discussing how to run PHP and Symfony on AWS Lambda. I was lucky enough to grab him for an hour to expand upon his interesting talk and the experiences he has had going Serverless with Symfony.
Symfony’s long term support for v2.8 ends in November. Eek! Quite a substantial part of our codebase relies heavily on 2.8 and some of it can’t be updated yet.
We can’t yet make the jump to v4, so we settled on upgrading Symfony to v3.4. In this short article I’ll describe how I stumbled over a completely unexpected problem with overwriting a standard password encoder used in user/password authentication.