Project Rescue

Project Rescue

From the Zend framework, Magento, bespoke PHP right up to the latest Symphony framework we’ve had to get stuck in order to help a client out rescuing their servers and code.  On a few occasions we have had to act within legal time frames, migrating servers and gigs of S3 storage right up to the wire.  Roughly once a year this comes up, and the same old question always pops up.  ‘Who has control of the domain name?’


More often than not this is a common issue, with as far as an old employee who left nearly a decade ago, still had control.

 

Most of the time, we are lucky to get a database dump and the application code.  This is often a zip file with limited documentation.  This is where the fun begins.

 

We go straight into dockerising (dockerizing with the zee for the USA folk) the project, checking composer.json for PHP versions and what it depends on, as this is the quickest way to get versions of software settled down.

 

docker-compose.yml can be a thing of beauty and can be bastardised into a mess but it never has to be.  Separating everything out as much as you can is paramount, not just one container running the entire stack.  That in itself is an achievement, and we’ve seen it done.

 

We even cringe running node within an php-alphine container.  Only due to time constraints we had to submit, as the php application was running mjml to generate emails which required php to run mjml through node.  At the time, we couldn’t find an api for mjml to be ran outside of php unless it was paid for.  We had to install node inside a php container.

 

But hey, we are engineers, we solve these problems in the environment and conditions we are presented with.  With infinite time and money, yes, but in reality all clients have limited resources, as do we.

 

We’ve never let a client down with a migration, or rescuing their project.  Things have been tight, but we always grind it out and get it over the line.

 

Conclusion

 

I conclude that this conclusion is here and only here for SEO reasons.  Therefore I conclude this conclusion with the fact I believe most conclusions are pointless and the writer believes their conclusion is what makes good content.