Next week I have to start an update of a Laravel API written with version 7 to version 11. I'm thinking of creating a new project then porting over the code then updating what's needed. Think it might be the less painful action.
What say you fellow Laravel Devs? Is there a better approach I'm missing?
Michael Wilkinson
@MichaelW_dev
Owner of Electrocode Ltd. Full stack developer building products on all platforms.
• 6 Posts • 8 Views
Your last paragraph is a brilliant shout. With the codebase being a few years old, it could do with a good review to see what can be improved.
As for the complexity of the project as a whole, it's fairly straightforward with simple models and controllers along with quite a few jobs that Laravel Horizon keeps an eye on. It uses the laravel-permission package from Spatie which will need updating but that's about the most complicated part. It might be a good project for me to use as my first go with Shift...🤔
Just signed up to this. It's bee-yew-tee-full 😍 and works brilliantly on mobile too. Great work! 👏👏👏