I am surpriced that programmers can create such a cool tool like Laravel Shift nowadays. So, of course, I'd pay for that cuz it worth it! Thanks for the video :)
With all the projects you do you should look for the docker version. Only twice as much but then it runs locally on your own machine using docker so you can easily rerun it with a new project without having to pay for each repo.
If the cases is like yours (update to match L9 style), then I'll gladly merge it. Because it will make the code standard across the project. Especially for auto generated file like migration. Aside from that, newer version of Laravel will continue to improve the previous version, including stuff like naming etc. By merging it, I think we'll prepare the app for the future as well. My main consideration will be, will it broke my app? If no, then I'll gladly merge it.
You don't have to buy it to find out. It's more of what's the case. cos if ain't broke then don't fix it. Equally you wouldn't get this for a one of code project you were playing with. But if you do have a long term project with some requirements that are only possible or easier when you upgrade them getting it makes total sense. And you have to consider the technical benefit of having consistency and standardization in your code base to be flixible. One you go through the effort of getting your code base into the right shape for such a tool. It simplifies and standardizes much of your future work. Why do all teslas look nearly the same or spaceX recently flew a falcon heavy booster as a full falcon 9 rocket. Even if you don't get such a product for your code base now. At least consider the relevance of making it suitable for tomorrow's code base or even making the effort to refactor given your health and brain extra points for the future
I would say it’s worth it. And you also supoorting his open source blueprint project. One of the project that I mainly used before using quick admin panel.
Just inherited a project on L5.4 - not looking forward to any option but excited by shift - I may come out the other end with a nice clean working system - defo run all the changes offered as its had various fingers poking inside leaving a trail of mess! ;-)
@@fredrickmakoffu2412 no - the business is prioritising new development over stability! Let me know if you try it as at the moment it seems my only option
making old code only work without respecting other changes may hurt later making future upgrades harder, just like technically you can ignore deprecation warnings now but you will have to take care of them at some point so why not do that as soon as they appear?
It's an interesting tool but does it handle custom project structure or just standard one? I guess I would use it if a project is really big and worth it. The PHP CS Fixer does most of these changes automatically. If I upgrade a project I usually use the PHPStorm power to refactor all the changes. I add Laravel repo as an additional origin and just diff-compare everything like default files, configs and etc in a moment.
Would love to see a video on how to switch from Laravel UI to Laravel Breeze/Jetstream. I know that Breeze/Jetstream are meant to be used for new projects but would be nice to get the newer features of Breeze/Jetstream in these legacy projects.
Breeze has actually the same amount of functionality as UI. So why switch? You prefer Tailwind over Bootstrap? And Jetstream is a totally other league, it's a full application and not starter kit. It's like upgrading from 1980 vw golf to 2022 tesla.
@@LaravelDaily Too much work for too little reward I suppose. Thanks for taking your time though to at least response. I really appreciate all your videos. 🙏
I have some automátions because I've been moving and old code base started by someone and it has kinks that I'm still finding out. Shift would definitely be a good tool to have if I did not have my own automation scripts. It does take me longer about a day from validation on local then staging validation with tests and letting the staging run for a few hours without issues before prod deployment
Would I pay 19$ for it? Absolutely. Obviously this is not for beginner project (Basic CRUDs etc) Yes you can use it for those types of projects as well but as you said as well, it will not be worth for small projects. But if you do have mid-sized project and above then I think this is so worth. Best part is, you can accept and decline suggestions as well. Would I accept all changes? Based on what I saw on your video, Yes.
Just tried this on my current project and it almost worked. See, I'm using laravel-modules to split my application into logical sections and whilst Laravel Shift correctly (almost) converted the "standard" part of the app to L9, the modules part was ignored. This "module confusion" also cause an error since the use statement pointing to the user class (in one of the modules) at the top of config/auth.php was removed. Thus the application could no longer find the user class and the authentication failed. An easy fix but should really have been left alone since there were warnings in the pull request stating that some things could not be processed due to the modular nature of the app. Still, it did a pretty good job and I can tidy up the modules manually easily enough. Certainly worth the $19 or whatever that is in real money (GBP) .
@@syamjulio3685 Yes, that's the one. It needs to be modified slightly to work properly as it is not updated very often, but it works well enough for my purposes.
How big's your project and how many changes did you see? I have a feeling my project will be too small to see a lot of changes, so the 15 quid might just work out at £5 a line.
No need to manually update the vendor files. Just update the version number of package in composer.json to the latest version, and files of that package in vendor folder will automatically be refreshed after runing "composer update" command. That's how updating packages works.
I think laravel should have a upgrade module or compatibility module before they release to a new laravel version. Why NOT? is my question. I mean even windows have a free upgrade tool !
An upgrade tool would be helpful but given every Laravel project is different from the next and each developer adopts different styles and syntax. An upgrade tool would therefore be complex to maintain and therefore agree with the maintainers decision to offer an upgrade guide with each release instead. JMac's Laravel shift is amazing and slightly opinionated and given the heat generated by Jetstream with L8 might be best done by the community as opposed to a first party tool. My 2 cents 😁
But open source needs to survive somehow, creating such upgrade tool (and maintaining it constantly!) is VERY time consuming, who would pay for that time? In the end it would end up as a paid tool like Forge or Nova, just officially supported.
@@LaravelDaily I guess we need some middle ground basic free package to update repo but need more advanced L9 compatible code? join paid. But we don't have any option except to do it all with our hands or start a new project with L9.
I have the feeling that Laravel is becoming a bit expensive as you need more and more tools to build project as fast as the people who use all these automated tools. I wish a company could apply for EU funds and start their own open source Laravel upgrade tools as I just checked the prices of Laravel Shift, it is just too much for multiple personal projects.
