Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.

remeritus's avatar

Maintaining Laravel App

I have successfully launch my first commercial Laravel project and have some questions regarding maintenance of it. Basically it has been worked on for about a year now during that period i was just pushing out features and not really paying attention to keeping everything up-to-date. Now project is up and running for about 3 months and everything is working fine, users are rolling in and there are no functionality issues.

However I can see that Laravel has since moved to version 7 (I'm running 5.8) I am getting warnings like Package X is abandoned, you should avoid using it. Use Y instead. I feel like I am asking for trouble if I just keep on working on new features but core of my app stay stagnant.

Now I have build up a bit of fear to just update everything in case it might break something.

Are my worries unreasonable and should I just go ahead with it? Or if it isn't broken don't fix it philosophy is acceptable approach?

PS: I was looking around the web but didn't find many resources on this subject, laracasts and docs did a great job of getting me up and running with Laravel ecosystem and allowed me do build something I wouldn't even dream of 2 years ago, but didn't really give me clear picture how to take care of it, could anyone recommend something on that subject?

0 likes
3 replies
martinbean's avatar

@remeritus It depends on your time, budget, and any external factors (do you have investors/stakeholders demanding new features delivered by a certain time)?

If you do decide to start updating the framework, do it in a step-by-step approach. So upgrade from Laravel 5.8 to 6.x, roll that out to production and let it bed in for a couple of weeks to see if there are any problems. Then, upgrade from 6.x to 7.x.

Trying to go from 5.8 to 7.x may be too big a jump and if you do get errors, you’ve got a lot bigger scope to hunt the issue down than if you just went one version at a time.

Tjyoung's avatar

I had same issue but was stuck at 5.0 Was basically impossible to upgrade as it was so far gone and ended up rewriting on 7 for four months. Lesson learned. Good to have a plan in place from day one

Please or to participate in this conversation.