Application upgrade
Is your application running on an old version?
I make it secure, and changes to it will cost you less.
PHP 7, Symfony 4 or 5, an abandoned library: as long as it works, nobody touches it. But vulnerabilities are no longer fixed there. One day, the host drops the old version of PHP. And every new feature costs more and more.
The longer you wait, the longer it takes. Moving to the next version takes a few days. Catching up on four at once can take weeks.
I move to a recent version, step by step
I start with an assessment: where the application stands, what is blocking, and how much it will cost. You know the price and the timeline before we start.
Then I move up one version at a time. At each step, I check that everything works as before. Meanwhile, you keep using the application: the new version only arrives when it is ready.
- Moving from PHP 7 to PHP 8, and to later versions
- Symfony upgrades, even from a very old version
- Replacement of abandoned libraries
- Tests added to check that nothing has changed
- Custom WordPress sites: theme, plugins and PHP
Pricing
Quote on request
The assessment gives the price: you know it before I start.
Discuss your projectThe technologies I update
I use them every day and I keep up with their new versions.
PHP 8
Moving from PHP 5 or 7: removed functions, extensions to adapt.
Symfony
Upgrades one version after another, and replacing what has been removed.
Doctrine
What changes in the database from one version to the next.
Composer and dependencies
Abandoned libraries replaced, security alerts fixed.
WordPress
Custom themes and plugins adapted to recent PHP versions.
Docker and deployment
An exact copy of your server, to test the new version before putting it live.
How it works
1. An assessment: where the application stands, what is blocking, the price
2. A copy of the application, so as not to touch the one you use
3. The update, step by step, checked every time
4. Going live, whenever you want
Still have questions?
I answer all your questions.
-
Will my application stop during the update?
No. I work on a copy. Your application stays online until the switch, which takes a few minutes, at a time you choose.
-
Why not rebuild everything?
Because it costs a lot more. And you would have to rediscover every rule the application already follows, even the ones nobody wrote down. An update keeps what works.
If part of it is not worth keeping, I will tell you, with the price of both options.
-
My application was built by someone else, is that a problem?
No, that is the most common case. I read the code before proposing anything, even if there is no documentation.
-
Does an update fix security vulnerabilities?
It fixes those in the old versions, and that is often the most important part. To find the other vulnerabilities, there is the security audit.
-
How do I keep this from happening again?
By making small, regular updates. They cost far less than a big catch-up every five years. I can take care of them under a maintenance contract.