We have our site running on Laravel 4.2 and have been thinking about upgrading to 5.0 for a long time now.
We also have a subdomain that we started building and decided to use Laravel 5.1 so that we could get used to it before the migration. We have the sub domain setup and installed and it is running.
However, our login does not persist between the two domains. We have the domain set in session settings on both systems. The cookie gets set but I am assuming Laravel 4.2 and 5.1 have different auth systems therefore the cookie from 4.2 does not work in 5.1 and vice versa. We have also tried database sessions and file sessions without much luck.
Is there a way to convert a Laravel 4 session into a Laravel 5 session so that users can go from our 4.2 main site to our 5.1 sub domain easily?
Is it possible to make both types of cookie one for the 4.2 and one for the 5.1 at the same time so that users would have and use both domains?
Or are we looking at this all wrong and should try something totally different to get what we want?
Or are we looking at this all wrong and should try something totally different to get what we want?
Do you really need to run 4.2 & 5.1?
Personally I've done a few upgrades from 4.2 to 5.1 (and even 4.2 to 5.3 recently). Your best bet is just dedicate 3-4 hours (or even 1-2 days depending on the size of your app) and follow the upgrade guide: https://laravel.com/docs/5.1/upgrade#upgrade-5.0
If you follow each step systematically - it is a fairly easy upgrade path.
Then put the 5.1 application in a sub-domain and have some users "test" the new version, before you push it into production.
There is also the Laravel Shift paid option as well: https://laravelshift.com/
Watchout, Laravel 5.1 use a new Hash system, watch the line
'cipher' => 'AES-256-CBC',
in config/app.php and compare with the old app.php
Related
today I have two similar Laravel projects, they are exactly the same except for the Laravel version, the first is running on 5.5, and the second is the updated version running on Laravel 9. The Laravel 9 one is not in production because we need a way to test it and check if everything is working after the update. My question is if there's a way to redirect to some clients only the newer version. The projects for the clients are exactly the same.
In conclusion I need a way to show to like 20% of the clients the newer version, and the older version for the other 80%, is possible to do this? Is there a better way to test the newer project for errors?
Thanks in advance.
You can use a Content Delivery Network e.g Cloudflare or something like AWS' CloudFront. You will be able to then configure the quota's in terms of where the relevant traffic will be redirected to.
Here is a link to an article on Cloudflare
and another one on AWS
You can also check with your host on how to configure a similar setup.
All the best
I'm currently in the process of upgrading a Laravel 5.2 project (yes, I know, I know...) to the latest Laravel version (9 at the time of writing). This project uses Caffeinated/Modules to structure the code - currently on version 3.
On checking the compatibilities using Laravel Shift, it appears there is no version of Caffeinated/Modules compatible with Laravel 9. In addition, on checking the Modules project on GitHub, no updates have been made to it in the past year - which is slightly worrying.
So I'm wondering if this plugin is effectively obsolete? (or soon-to-be?)
Does anyone know if there are any plans to keep it going in the future? Or is it worth ditching it now?
(For background, I tried a single "shift" from 5.2 to 5.3, and so far have been unable to get the Module routes to work. I wonder if the Modules could be the biggest headache in the upgrade process).
Any insider knowledge/advice/experience gratefully received!
I want to use jetstream for auth.
I create the project earlier and already worked on it. Now I want to use jetstream.
But in the official documentation of jetstream I found this warning:
"New Applications Only
Jetstream should only be installed into new Laravel applications. Attempting to install Jetstream into an existing Laravel application will result in unexpected behavior and issues."
Now I want suggestions that how I can use jetsteam without any issue in my existing project.
probably there should be no problem if you are using git . just commit your latest changes and add jet stream .
there is an issue on Jetstream GitHub page about it
Please, give red visible warning for peoples, that Jetstream will overwrite your existing work, and it is meant to be install only on fresh installations.
check it out
update :
well , I have added Jetstream to my existing project which working on it for four months , there was a problem with font awesome Vue version which deleted that and going to add it again with newer version
, there was some bugs but was easy to resolve , so if you backup your project its totally ok and works fine , but you have to setup your project again with previous tasks you have done before
How does one downgrade a Laravel 5 project to Laravel 4? If it's not that hard, it might work better for my team. Any changes in Eloquent, Controllers, views, and user logins would be the need-to-know. The primary reason we are looking to downgrade is host PHP support. 5.3/5.4 are what we'd need, so whichever version of 4 we use would need to go that far back - I guess I'm also looking for advice on which version of 4 would be good.
I have just tried with Laravel 4.1 using a project which I half way develop with Laravel 4.0. After I move everything over to clean new Laravel 4.1, everything running ok. However, one thing that is truly unacceptable is the slowness of Laravel 4.1. All webpages loads extremely slow. Everything I tried were running on my local PC with WampServer.
On Laravel 4.0, a webpage take about 97ms to load. However, on Laravel 4.1, the same page take about 1.14s to load. It is more than 10 times slower.
Do you experience the same problem like me on new Laravel? Is there any possible I can improve the speed?
Thanks.
Just try to upgrade your Apache Server. It should run faster.
If you are using MySql then check your config. Is the host set to "localhost"? Try to change it to 127.0.0.1. See WAMP/XAMPP is responding very slow over localhost for more.