Auth in Laravel 8: Fortify and Laravel UI (without Jetstream)

[@LaravelDaily]

Liked this video? I have many more: subscribe to my 30+ Laravel courses laraveldaily.teachable.com/p/all-courses-yearly-membership

Is cool that you are a critic inside the Laravel community, really help me to learn more and understand things better. This videos is just awesome.

[@PovilasKorop]

Thanks Francisco, such comments give me additional motivation to keep going!

[@yassershahine7445]

I am like new comer to Laravel.. I started learning Laravel 7 and quickly I faced Laravel 8. I was In a chaos situation and your video really really HELPED me a lot. THANK YOU sir.

[@ShabbeyRoadMusic]

There's no rule that says you must use the latest version. They change this product too quickly for my purposes & I'm not willing to sacrifice valuable business development just to learn their latest thing.

[@yassershahine7445]

@@ShabbeyRoadMusic They made the release of new versions every year instead of 6 months. Enjoy!

[@ShabeebRizvi]

Good job! Would love to see a complete video (frontend using bootstrap and fortify) on HOW TO ENABLE TWO FACTOR VERIFICATION without JetStream! Thanks 🙏

[@JohnSmith-zl8rz]

Exactly, how HOW TO ENABLE TWO FACTOR VERIFICATION without JetStream! or User Delete his own account.

[@ShabeebRizvi]

John Smith I have the very same question! Probably will try to look into it this weekend! 😊

[@wolli87]

Found your channel a few days ago. Really nice content and good in-depth explanations to the Laravel-Cosmos. Keep up the good work!

[@PovilasKorop]

Thanks, Wolli! Yeah I'm flying through that Cosmos and shooting video on things I find along the way :)

[@TechnoTrace]

You know something, it's very easy when someone like you is making the concepts clear about the changes in the technology. Because most of the time I don't get to read all the documentation and also don't know the tricks to follow when creating a new project with new laravel. Your support is utmost important to us because when the technology changes suddenly then it becomes a disaster for us to create new projects quickly as it is most often required with running clients, you know ☺️☺️.🙏🙏 I'm very pledged to have your support Povilas.🙏🙏 I also follow you on LinkedIn and here on KZbin. Please continue to inform about the ways to improve time and quality on laravel projects as you do. Continue your great work Povilas 🙏🙏.☺️ I'm Techno Trace. Peace👍

[@PovilasKorop]

Thanks for the support, I feel that community need such videos from me, so will keep shooting them :)

[@TechnoTrace]

@@PovilasKorop ❤️❤️❤️❤️❤️❤️❤️❤️❤️☺️☺️🙏🙏

[@fatih-araz]

Great video. I don't like updates where you have to learn new frameworks where you have to mix all the js frameworks. But this video explains perfect how to work with your preffered js pramework. Great video!

[@phread6691]

Thank you, thank you, thank you!!!!!! After reading that the old UI was deprecated, I was quite concerned about what I thought I had to do. I have enough going on and dealing with the new auth system was just not going to fit in my schedule anytime soon. However, thanks to you I will be able to upgrade to Fortify quickly and easily. Your description and step by step procedure helped a LOT. While I am not happy about this change, I do understand why the change was implemented. It makes a lot of sense now and seems to be a much better process than what we did before 8.x. Your video, as always, was/is a fantastic help!!!!!!! Thank you!

[@axeman2638]

Laravel is changing too fast for anyone to keep up, the documentation is lagging and it's looking like feature creep is the current model of development.

[@LeTrolli]

Never use anything else than the basic framework and one or more very specific and useful plugins. Laravel UI, Fortify, ... are completely useless.

[@nishantgupta1854]

@@LeTrolli yea in long term these are pretty uselss

[@JohnSmith-zl8rz]

@@LeTrolli Curious, so what do you use for auth? or views? Nuxt? or?

[@markusschindler4376]

@@LeTrolli totally agree

[@pietrobattiston6667]

All these changes are making my developer experience with Laravel very frustrating

[@levonorrr]

I love the way Povilas loves Laravel but he's professional enough to say publicly what he doesn't like about the new changes. This video helped me a lot to understand the changes because I have been using Laravel since 4.2 and it has never been so difficult to understand the documentation, I remember that before it was not even necessary to install packages, only Laravel and that's it.

[@levonorrr]

After I wrote the comment I realized there is a third package called Breeze, as I understood, this package solves the problem of copy/paste the views from another project.

[@SunilKumawatbfcj]

No one knows what will happen in the update, but I am sure you will be available to help us. Thank you for the help and support. 🙏

[@2008rol]

I think Laravel auth changes too fast. I still like php artisan make:auth

[@lexxluey]

@Madushan Jayawardane COSIGNED

[@luiejohnmalimit]

I was looking for this. It all became clear to me with all the laravel mess.

[@dezetzede1382]

Penjelasannya singkat padat dan mudah untuk saya sebagai nubie untuk belajar. Alternatif menggunakan fortify, livewire lebih mudah bagi nubie.

[@arniep0123]

Thank you so much for this explanation. I was frustrated thinking I was being "forced" down a certain tech stack. This makes perfect sense the direction the Laravel team is taking. Great vid.

[@ShabbeyRoadMusic]

I think Laravel has been gently "forcing" people toward certain stacks for several versions. I don't think I'm even going to bother with Laravel 8. I installed L7, am watching vid for Laravel 6 (cuz there's not really a comprehensive vid for v7) and will most likely stick with that. I agree with everyone saying it's changing too fast. Feels like someone just said "Let's release a new version every xx months" without any real justification. At some point, it needs to "mature" or people will find something more stable.

[@trueyolu1906]

Thank you very much! Your videos is amazing, everytime you give away something new. From your videos Im learn not only Laravel, but also best practices in code and how right to think.

[@whatdaro]

Thank you, you are a legend. Finally a video that not only explains what all the different parts are but also provides a clear and easy example how to implement the solution. Subscribed!

[@joshbarros1995]

Thanks a lot for this tutorial! I'll try this with Vue2, Vuex, Bootstrap5 tomorrow! A more "hybrid" laravel approach... without Inertia.

[@JustMillIt23]

While copying the public css and js is a good temporary solution, I ended up having to require laravel/ui in the new app with fortify and run php artisan ui bootstrap, followed by npm install && npm run dev to get the changes to stick in the new app. GREAT TUTORIAL! THANK YOU!

[@emranitan6221]

i hope you read my comment ....lens you are great person i dont know what to say but really thank you from my heart ,,,,,helping ppl is great thing

[@impulserr]

So thats not only me who got confused by new auth ;) I prefered much more old way, generate auth with just simple bootstrap views. From simple framework auth generation they changed it into "you need to find your workaround" ;p

[@cburg]

Thank you so much for this. Was having real trouble following older tutorials for auth, this was incredibly clear!

[@megh219]

great video. I understand the whole fortify fiasco much better now.

[@smkishtiak]

A lot of things were made clear in this video! Thanks a ton!

[@fylzero]

This video is amazingly helpful. Thank you for all you do, good sir!

[@TheOne13337]

I hate the direction where Laravel is going. I loved how before all the routes were in the route file and you had full control of everything. Now all the auth routes are included with oneliner and it is harder to modify those routes if you need to.

[@theekingyodah1431]

this was really helpful , clearly explained 💯

[@chiragdabhi07]

thank you sir helpful video is beginner

[@sethhene6730]

Wow, this is soo helpful. Thanks for this tutorial, keep up the good work

[@bhaidar]

Amazing videos as always! Can you share with us a video on implementing a Multi-tenant app in Laravel, either from scratch or using/setting up a good package? Thanks

[@kbenanos8626]

Please can you do a video on multi authentication with laravel 8?

[@flamme8587]

im gonna keep ui+adminlte login views this combo always worked for me

[@Xirismenos]

Great tutorial! I have a big problem. How to configure routes and change the default login, register etc? How to separate roles users and admins into different tables? Is there any lesson to customize this package or any package from the composer?

[@ShabeebRizvi]

Exactly what i have been waiting for... LOL Need to checkout Thanks!!!

[@paweupawel8890]

you really explained very well

[@HaizadAnnuar]

Hi, I liked on the part that you mentioned Laravel stays as a backend framework 11:58 . But can I just use Lumen as the backend? What makes Lumen different from the others? I was thinking to build app using Lumen as backend with Vue.js or other Laravel project as frontend. Do you think that Lumen is a good choice and relevant to use on these days? Thank you.

[@PovilasKorop]

Lumen 8 has been just released, and read the comments under that post, you will get the picture: www.reddit.com/r/laravel/comments/itw39p/lumen_80_has_been_tagged_and_released/ Personally, I never used Lumen and never really understood its purpose.

[@HaizadAnnuar]

@@PovilasKorop Thanks for sharing the link :)

[@lwandilerozani8592]

What an interesting date choice to release a new Laravel package 🤔

[@wandyy.d1235]

Hi there! Thanks A LOT for your video (information) I want to put it as one-word - COMMUNICATION Kind of agree with you in this video (on the latest section about Laravel 8) and as @Thinkverse mentioned (on your pinned comment). Please, correct me if I'm wrong on my personal opinion on how they should handle this - Not to offense Laravel 8 team with their sudden changes, maybe, they should doing a kind of BETA TEST - which open to public, so everyone can see / check what they did in the coming version. Think about it as a OPEN BETA TEST on the game, where players can play the game and expecting - "Ohh there's bug, it's okay, I know this is a BETA game, so now, I will let them know about this bug and hopefully the Dev team can check and fix this". Maybe they can limit WHO or HOW many people - can join the BETA TEST, so there won't be too many comments / feedback on BETA TEST. I don't want to compare one product with others, but, let's take a look as an example - Bootstrap 5 (I think most of us already notice that), they didn't just release that to public, without any prior notes or documentation. Rather, they let all of the user know "Hey, Bootstrap 5 is here soon! We put it on Alpha Test. We don't recommend you to use this on production yet, but, if you want to play around with it, here's the link to get it Bootstrap 5 Alpha" --- Apart from this little "chaos" - thanks to Laravel, I got sooo many experience in building web application / else - because of them, I got to a level where I can learn how to "learn" things around FYI - first time after a very very long time, I'm just a watcher (someone who's just watching youtube video without commenting / like) - and this video makes me want to comment and giving a support to this community (this channel and Laravel).

[@PovilasKorop]

Yes, I've pinned Thinkverse's comment because he expressed what I thought in an even better way than I would have. And I agree very much with your thought, too (thank you for such a long comment, by the way). Laravel way of launching things has been always like Apple or a similar company, with some marketing effect - some secrets with anticipation growing, and then BOOM - we have something new (Nova, Spark or whatever at that time). It has the marketing effect for sure, but in this case, it wasn't just a NEW tool presented - it was CHANGING OF THE OLD TOOL. And for this case, specifically, I do agree they needed to approach it differently, slowly, and more openly from the beginning, and not launching docs/articles AFTER SHITSTORM BEGAN. I hope Taylor will learn something from it, that it's not only about cool tools he's launching, but also taking care of the old LOYAL users of the framework who don't necessarily want to switch to new tools. As a framework, it needs to have as few surprises as possible, otherwise in the long run clients/developers won't trust it as a future-proof solution.

[@wandyy.d1235]

Right! The Apple strat! (I was wondering what it is, since it feels something similar before) In this particular case, that strategy is not really good, instead, giving a little "chaos" to themself and of course us I do really agree with your statements, especially about the "future-proof". At the moment, I couldn't make many movement related to Laravel and closely watch their updates and see what else being adjusted Aside of this, let's continue to support the community and hope they won't surprise us with any "chaos" again Thanks again for your insight!

[@megavolkan]

What i'm really confused about Laravel is that they add new features that are too obvious to be removed/ditched in near future versions. For example UI forms abandoned, Bootstrap is abandoned. I'm sure Tailwind will be abandoned too at some point. I'm open to changes (and change is good/inevitable) but when it comes to Laravel i feel like Laravel is not something to rely on. Pushing out auth scaffolding with mandatory js (and css like tailwind) is not good. I'm a php developer but what if i'm not preferring to learn js frameworks? Do i have to? Obviously not. Would it be good for me? Why not, but i have no time right now. What i learned about Laravel is if anything is related to ui it will be ditched sooner or later.

[@Alihamza-cf6ty]

Thanks for such helping video

[@GujaratiMotivationFacts]

Thank you so much for this.

[@chhunheangpin6421]

Thank you for the video!!

[@jfarber55]

I do the same with Laravel 10.1, copy all blade files from ui installation into my new laravel proyect with fortify. I only needed to install some packages via npm like saas, bootstrap & popperjs/core. Next of this, all the instructions runs perfect and I have my proyect already with Fortify and Blade (ui blade files copied)

[@ervanrhermawan2380]

I already followed steps on Generate view for Fortify (8:46) but I keep getting the same view like in 9:41 can you help me with that? thanks

[@eugenemirt4921]

Hello. Can you make a video about authentication using only Auth? I'm confusion why we need to use staff like Fortify that are unreadable (ex views located in providers). Can we just make controller and view? im missing somthing?

[@alienheartz9163]

Hi, thank you for a great tutorial. I have question, currently I'm using Inertia.js + react and I created login and registration manually. What about password reset or e-mail confirmation? How can I do manually? Should I install some package or Laravel has built in function to handle this? Best regards.

[@alienheartz9163]

I actually saw the documentation hahaha, nevermind , thank you for tutorial and have a great day!

[@gianlucasgalati1008]

is there a way to use a vue/react view like a login with inertia js and implement it with fortify? Currenty i installed jetstream and fortify and by default the /login route goes to a blade created by jetstream

[@alienheartz9163]

@@gianlucasgalati1008 I created login view and etc. based on React with Inertia.js, but I didn't use fortify. If you want to just have a simple registration/login, you can do it manually by reading a docs of laravel. I will check the fortify and let you know what we can do with it.

[@larslommen9098]

Really helpful, thanks

[@1309CV]

My current problem with the new scaffolding, and Fortify in general, is a lack of obvious (or clear) control and customization. With Laravel UI, the controllers were available to us on the fly, and were (arguably) a clean and fast approach to take control of the authentication pipeline, and customize the process for your project needs. We now have to follow an awkward path to take back control. Changing things in the boot method feels 'wrong', tedious, and isn't that clean. It's a frontend agnostic authentication, so that's a nice focus back on to backend. That part is a step in the right direction. Everything else I mentioned above, however, feels like a step backward.

[@himanilsharma2147]

also I had went through your other video of using laravel ui and auth pages are not applied with any css, So I went to git and search in the laravel ui project and found css and js files were missing in my project, However I copied them in my project folder but they are not being used up by project !! :/ I changed I extension of one file with .scss to css nothing happens except resolving syntax errors in .scss file. Its been 8 days and I am struggling with just understanding how this auth thing will actually work properly... Whereas in php, in 8 days I had learnt it from scratch and made a billing project!! Please suggest what should I do... I am being hopeless day by day

[@CalicoArchives]

I wish Jetstream had a plain HTML option.

[@Pb-pj8ft]

After logging in, the profile menu doesnt dropdown. Also what about the logout functionality?

[@BudiSantoso-er6cq]

Great video, thanks Master. God bless you..

[@nargeshrana3740]

Thanks! video is very useful.

[@dmdk8301]

I am totally confused after Laravel 8. What if difference between Fortify and Sanctum? Do i need both of them for my SPA project? In Laravel6+Nuxt|Vue i used passport for tokens. And now i cannot even start( Laravel was really great and quite easy to start. Now - its a quest((

[@Kalexy91]

Great video! Thanks man!

[@sparkqy135]

Can I set up Fortify to have multiple login/register routes? I need one for regular users and another one for admin (they should have different url and views).

[@marceloAK1]

Hi, thanks a lot for the videos!!! Is there any way to disable auto-login after registration? I want to add new users only using a registered user (like admin for example).

[@hosseinhaghparast5670]

is there any way to use 2fa with passport? i need to have both OAuth2 and 2fa in my applicatin

[@dayronbornot6153]

Hi Povilas. Its posible use directly the Fortify functions for customize my own views or the way to show them...for example, use a Livewire component and develop the 2FA reusing the Fortify code? Its possible?

[@PovilasKorop]

Possible, I think this is done similar github.com/zacksmash/fortify-ui

[@dayronbornot6153]

@@PovilasKorop I made it. I reused the jetstream TwoFactorAuthenticationForm with ConfirmPassword trait and works perfectly. Thx

[@JohnSmith-zl8rz]

I think Taylor was wrong when they say this "I doubt many people will use Fortify directly... mainly through Jetstream's usage of it."

[@jerrychian]

I'm very new for laravel and follow your video to to learn about everything, but after register the website i meet a problem with "These credentials do not match our records." I really sure about the every login information is correct!. so I don't know how to fixed , could you provide some suggestion to me?

[@ho6y]

How could you apply a guest middleware to Fortify?

[@Asifkhan-dl4so]

Thanks for the video

[@benedicthumpert5664]

Thank you! I almost threw Laravel in the garbage can ...

[@MiniPinho098]

Hi, thanks for the Video! however, I have the same bug as u at 5:54 minutes for the PHP artisan migrate but unlike u I don't know how to fix it... and I don't understand what those credentials are...

[@alisleem1626]

I founs ur channel recently and i really like it but i am little confused , can u make video telling us beginners where to start and how to make the best out of ur amazing videos 😄

[@marcinmaj3609]

What A mess with new auth...

[@OstapBrehin]

Then Breeze is for you

[@abcoolguy]

hi povilas, i tried laravel 8 with jetsteam and livewire. It doesnt seem to work on ie11. Any suggestions to fix this?

[@PovilasKorop]

I don't work with IE11, so no idea, sorry.

[@chamathviranga619]

thank you, you saved my day

[@youssh4975]

what if the login route redirects to a white page?

[@eokwukwe]

Thank you for another amazing tips as always. Is there a way to use fortify for RESTful API authentication? I am more of a backend guy.

[@PovilasKorop]

For RESTful API you have Sanctum/Passport, Fortify has nothing to do with API.

[@StoryOfTheReality]

I have some questions about Laravel 8. Could you answer me? 1. Why Laravel 8 choose Tailwind CSS over BootStrap? 2. Can I use Laravel Jetstream (inertia) with BootStrap instead of Tailwind? 3. Is Laravel Jetstream (inertia) can be useable with API also, Just calling the same URL from api.php?

[@PovilasKorop]

1. Because Taylor and the core Laravel team prefers Tailwind. But it doesn't restrict you from using Bootstrap with laravel/ui 2. There's no Bootstrap option in Jetstream 3. Probably, haven't tried.

[@StoryOfTheReality]

@@PovilasKorop Thanks. Is there any way to use BootStrap with JetStream?

[@gianfrancobriones]

11:46 "IT'S A MESS" It's a mess that I even skipped the login/auth functionality of my app and I'm already half-way through finishing it.

[@blog4lives]

I recently migrated from my current laravel 7 project to 8, is it advisable to get started with jetstream / fortify and how could you best do that with an existing project? So far I mainly find tutorials that start from a new project, but not from an existing project.

[@PovilasKorop]

For existing projects, you should not use them. Those packages are for quick START.

[@blog4lives]

@@PovilasKorop Hmm too bad there is no bootstrap support, must say that I would like to use that teams option and the 2 factor method

[@PovilasKorop]

@@blog4lives Those two are not THAT hard to implement without any Fortify. Much easier than change all your internal systems and switch to Fortify.

[@NirajGhimire]

If you love the old way (Laravel 6/7) of generating auth scaffolding in Laravel 8. Simply composer require laravel/ui php artisan ui vue --auth just remove the version of laravel/ui from laravel 6/7 documentation

[@tanzimibthesam5861]

It's good liking it but it will be deprecated in future as many says

[@NirajGhimire]

@@tanzimibthesam5861 nobody knows about future.

[@longpham6582]

I got a bad method call error. how to fix it now

[@jaydevgodvaishnav9433]

Thanks for help

[@dgloria]

Hi, I'm struggling with eloquent and want to head back to usual query, but first I ask you maybe you have some time to help me out. My issue is that I have a join table which has a foreign key that is related to more than one table, so that I can't name it drivers_id, because it is also related to three other tables. Is there a way to make a function to use this relationship where I determine the foreign key name, instead of ``` class Property extends Model { public function driver() { return $this->belongsTo('App\Driver'); } } ``` My foreign key is called properties.prop_link_id and not drivers_id that causes a problem, and I don't want to change it, because I won't be able to use it elsewhere. I can't find anything about this in the documentation, no complex queries are described there. Also I am struggling to decide where to store my complex queries if not in Controller and not in Model. I assume both should be kept tidy so my queries need a home to stay.

[@PovilasKorop]

You can do belongsto (App\Driver, prop_link_id) - second parameter is a field name

[@emmanuelugwuoke967]

Thank you for this video ☺️. Now I understand fortify more. How can we go about multiple auth scopes in fortify?

[@PovilasKorop]

Not sure, haven't tried.

[@emmanuelugwuoke967]

@@PovilasKorop alright. I look forward to more tutorials on fortify 🤞

[@youssefamad88]

Thank you so much

[@raghavkumar6292]

Hi sir how to handle the kyc data of already existing project in larvel

[@marcopilaric4257]

Is there a way to make the email verification link in fortify work only once?

[@creeddm]

How would you setup authentication for laravel 8 API only app with separate frontend like Nuxt? Would you still use Fortify for that?

[@PovilasKorop]

I wouldn't change anything, would use the same old Auth with Laravel Sanctum, Fortify is optional.

[@lordgodgiven]

Hello, I'd like you know how create a lockscreen, such as on windows, instead of to close session, i just lock it and when i want to use computer, just enter password

[@princeacheampong2837]

How do I manage the users created here

[@issaissifou3579]

Thank you!

[@robdorn420]

Thank you again for making a great informative video. Can you please make a video about how to create traditional vue.js views in Laravel 8, without the use of inertia.js? That would speed up my conversion from Laravel 7 to Laravel 8 in the near future. I dislike the idea to convert to much to accommodate inertia.js.

[@PovilasKorop]

Nothing actually changed in Laravel itself. You can use the same Vue as you did before, Inertia is required as one of the options only if you use Jetstream for scaffolding. Which, as I've shown in this video, you don't HAVE to do. It's optional.

[@robdorn420]

@@PovilasKorop Thank you, then I will go and start using 8 asap:)

[@nikhilagrawal2507]

*Useful video* Nice trick :) :)

[@itacademy7016]

Sir, I have a newbie question. I've installed Laravel Sanctum after all that and don't know how to createToken() as it said here(laravel.com/docs/8.x/sanctum#api-token-authentication). Should I use my own "login system'" in my case or could you suggest anything, please ? Also is it desirable or not to change non-project files(Fortify files) ?

[@PovilasKorop]

Your question has so many sub-questions inside that I definitely don't have an answer for you. Sanctum API tokens are not for "login system", they are for authentication with API tokens, not sure if you need other login system, it depends on your project. Fortify is a separate thing from Sanctum, not sure why you're mixing it into the same question. Overall, to understand, you need to find practical examples online about Sanctum online (and probably specific about API Token Auth as you chose to use it), and learn from them. Impossible to help you in a short comment.

[@itacademy7016]

@@PovilasKorop Big thanks for the response. I need Sanctum to protect api routes in my case. I've watched your video(kzbin.info/www/bejne/naq6faumjryrfLM). Here, you created the token with Tinker. Using Fortify, I don't know how to create token while user is logging in.

[@PovilasKorop]

@@itacademy7016 I don't know either, sorry, I haven't used Sanctum with Fortify.

[@itacademy7016]

​@@PovilasKorop Wish your channel even more prosperity. keep it up !

[@mrpmac]

I was all onboard and pumped for this solution until the step where you copied and pasted all the old auth & layouts view directories from somewhere else. I like creating Laravel projects from scratch easily. I sure do miss the old --auth option.

[@pumpkinhead6646]

What did you end up doing with your set-up then?

[@mrpmac]

@@pumpkinhead6646 Sadly, I spin up version 6, then pull in laravel/ui: composer create-project laravel/laravel ProjName 6.* composer require laravel/ui:^1.0 php artisan ui bootstrap --auth npm install npm run dev

[@kadirookirim3231]

thanks Sir .

[@earhackerdem]

I love this channel

[@warpig2786]

may be too late until i get back to the response but, what if i already had installed the "old" laravel auth, that is, without fortify, do i still have to remove all my auth created files back from when i used "laravel auth" ? Im a designer. Cheers.

[@PovilasKorop]

"old" laravel auth still works, nothing wrong with it, new things are just for new projects with Laravel 8 and they are all optional. Don't change anything.

[@warpig2786]

@@PovilasKorop thanks, now that I know this, and got what I wanted (email verification) would it be too late to just drop/uninstall, fortify?

[@PovilasKorop]

@@warpig2786 It depends then, there's no right answer, can't advise without analyzing the full code of your project.

[@LearnTogetherYT]

I think I'll stick to Laravel 7, I don't really think there's many benefits in upgrading !

[@tanzimibthesam5861]

Yup but it has no updates after a certain time if you don't experience bugs it's fine though but it's always good to use the latest versions

[@frandami1]

Laravel creator is a genius in terms of converting great ideas into laravel features, but he's also a jerk and a very rude person that can't take some criticism from people who were supporting laravel community.

[@Alturic]

So very true. His responses are "my way or the highway" typically.

[@eiroeiro2228]

yeah, like when he said - if you are not using these technologies, then there is new problem for you 0:53

[@michaeltruong2232]

@@eiroeiro2228 You are aware the guy in this video isn't the creator of Laravel right?

[@eiroeiro2228]

@@michaeltruong2232 Sorry, i wasn't - my bad.

[@tatendawilson510]

hie laravel business, did you upgrade quick admin panel using fortfy because i want to pay for my monthly subscription

[@PovilasKorop]

We did upgrade to Laravel 8 but we decided not to use Fortify yet, it's too early, and not too much documentation about its customizations. So good old trusted Auth is good for now.

[@kydva]

Thanks!!

[@CheapBurger]

Hi, currently my project still using laravel/ui auth , so how do i upgrade to fortify ? it possible ? thank you

[@PovilasKorop]

If you're using Laravel UI Auth, it's all good, you don't need to upgrade to Fortify, stick with what you have.

[@CheapBurger]

@@PovilasKorop thank you for the super valuable advice , my mind always tell me that the latest update is the best lol , because i see fortify look very cool and laravel team RECOMMEND us to use their jetstream with fortify xD

[@ShabbeyRoadMusic]

@@CheapBurger Dude, that is hardly ever true. The "latest update" is the one that typically still has problems or is not well-documented. Let somebody else use it & work out the bugs. I've found that to be true for almost every tool I've used over the last 25 years. I don't have time to "system test" new releases.

[@joincoder]

I can not catch your copy and past because not clearly path

[@bassamdarawshi]

what is the software you use to browse the db>??

[@PovilasKorop]

Sequel Pro

[@bassamdarawshi]

@@PovilasKorop thank you . is there any alternative software you recommend for windows ?

[@PovilasKorop]

@@bassamdarawshi don't know, sorry