I really appreciate the effort put into creating these longer videos, and I like the concept behind them. It's clear how challenging it must be. I’d love to see you dive even deeper into certain areas to really showcase the best practices. That way, we can pick up on those small but valuable tips and tricks that come from years of experience and working on numerous projects.
This is amazing, you should do this more. Create something fullstack production ready so we know how things work in production. Use all the clean code techniques if you can
Personally, I like the short version with suggestions better.. it keeps me company at breakfast.. but congratulations for the initiative that must have taken a lot of time
Please do more of longer version for laravel advance projects. Maybe put the repo behind the pay wall so that only premium members can access the repo and us brokie are gonna code along with the legend. Cheers. Thank you for this video.
This is a good model for my own personal preference. I’ll watch the premium vid first, and come here should I need expanded info on certain elements of the video. Good model, for me at least.
Great video, as always! I think I would have preferred the use of native Policies rather than Spatie's, because their operation is almost the same for this project, and it could be a great reminder of the View ViewAny methods etc, and by the way reduce the number of third parties libraries. But great work!
That's multi-language, it comes from /lang folder, or vendor translations in case of Breeze, from what I remember. Read more in the docs here: laravel.com/docs/11.x/localization
Why is your users table migration file already populated with field descriptions? A fresh install reveals a class with two empty methods, up() and down(). Where can that code be found or does it now need to be created from scratch? Thank you.
@@LaravelDaily I upgraded Herd to the latest version including PHP and let the UI of Herd do the installation. Migrations are blank. Where can I reference the database, row, and column information? It has to be somewhere since the tables were created when the site was created. Otherwise, I can delete the site and try a CLI installation. But it had to create the table somehow!
i like this approach! but i think this tutorial is not really for beginners, because you're navigating the project files way faster, which is very hard for a complete beginner. just my two cents. but for intermediate level laravel developers, this is a breathe of fresh air. nice work regardless!
This is the video where you get really off track. Sometimes you speak very quickly. Overall, it feels like I’m watching an amateur-made course. I hope in the future you focus less on profit and more on truly teaching people how to program.
Great video, as always. I have two questions on your project. # Database Concerning the following simplified DB schema: projects - user_id - client_id tasks - user_id - client_id - project_id Isn't projects.client_id and tasks.client_id redundant? With this setup, how do we ensure the two fields are "in sync"? # Factories I like your setup, like in project factory you have: $users = User::pluck('id'); return [ "user_id" => $users-random(), "name" => fake()->words(2, true), ]; But this means that we have to remember in which order we use the Factories. You cannot factory-create a Project unless you have created a user first. If we used "user_id" => User::factory() the order in which the factories are called doesn't matter. But at the same time, it makes our seeders more complex, beause we have to manually feed "sensible" relationships to the factories. What do you think?
Finally, a comment on the actual topic of the video! :) DB structure: you're right that you could get the relationship from parent's parent, but then it would be a slower query. In this project, I didn't build anything for them to be in sync but in real project I would do that with observers, probably and not show the dropdown in the form. With factories, those things are personal preferences.
Thank you very much, I started my career as Laravel developer by watching your videos
I really appreciate the effort put into creating these longer videos, and I like the concept behind them. It's clear how challenging it must be. I’d love to see you dive even deeper into certain areas to really showcase the best practices. That way, we can pick up on those small but valuable tips and tricks that come from years of experience and working on numerous projects.
Sharing this masterpiece with my students ❤
Thank you, Uncle Povilas 🎉
Great tutorial! This step-by-step guide is really helpful for beginners learning to build a CRM in Laravel. Please make more videos like this. Thanks!
please do more of this . i hope you do a long video and using service design pattern with DTOs and clean code .
This is amazing, you should do this more. Create something fullstack production ready so we know how things work in production. Use all the clean code techniques if you can
Please do more of this. This helps alot.
Personally, I like the short version with suggestions better.. it keeps me company at breakfast.. but congratulations for the initiative that must have taken a lot of time
this is great! like this one more than shorter and more specific ones. you cover a lot of things in just 1 hour. thanks from LV :)
I am ready for a 12 hours video
Thank you
I personally vote for more of these. Thank you for preparing this tutorial.
Please do more of longer version for laravel advance projects. Maybe put the repo behind the pay wall so that only premium members can access the repo and us brokie are gonna code along with the legend. Cheers. Thank you for this video.
great Povilas!! Super Idea with the hole projects! I am already member of Laraveldaily
This is a good model for my own personal preference. I’ll watch the premium vid first, and come here should I need expanded info on certain elements of the video. Good model, for me at least.
Great Idea and Content
Thank you so much for your efforts
That's a great project! I don't mind the longer video format
yep, finally someone does the subject in a comprehensible manner
great video for new developers, now please make one for advanced developers
I really like this new format, can you make more videos like this? I feel like I learn alot watching your work process :D thanks!
now we need a multi-tenant example long video too 👌
Thank you and continue shooting videos like this, it's a really great idea
Great video, as always! I think I would have preferred the use of native Policies rather than Spatie's, because their operation is almost the same for this project, and it could be a great reminder of the View ViewAny methods etc, and by the way reduce the number of third parties libraries. But great work!
Yeah, I actually thought the same in the end, that Spatie package for this simple use case is an overkill.
please more long videos
Thank you so much Povilas for this! Great content!
Thank you so mucch, yesterday i just appointmented to build Laravel project and dont know where to start
thanks for this practice🙏
Don't forget to restart your browser to update Chrome 😁
And of course, thanks a lot for your work!
Amazing ❤🎉 thanks
Perfect mayby samsing about api or pacage create
Great job, can you do something advance topic with this format?
For super-begginers it would be great to see the how too of a simple services website.
Thank you
It works well yea
stunning
Thank you for all you do sir.
Quick question please, how did you get your code to "fold" the way it does?
What do you mean by "fold"? Maybe you're talking about some feature of PhpStorm.
@@LaravelDaily I meant the way your code "slides" under their parent tags. Is that a feature of PHPStorm?
Still didn't understand, sorry. Send me a screenshot to povilas@laraveldaily.com :)
Thanks man :-)
💙💙💙
please do auth with cookie... i always got token xsrf mismatch or unauthenticated.... with laravel 11...
with laravel 10 all was fine
how does the {{ __('Profile") }} syntax work?
That's multi-language, it comes from /lang folder, or vendor translations in case of Breeze, from what I remember.
Read more in the docs here: laravel.com/docs/11.x/localization
Why is your users table migration file already populated with field descriptions? A fresh install reveals a class with two empty methods, up() and down(). Where can that code be found or does it now need to be created from scratch? Thank you.
No, fresh Laravel install has users table with all the fields. Not sure why it doesn't for you.
@@LaravelDaily I upgraded Herd to the latest version including PHP and let the UI of Herd do the installation. Migrations are blank. Where can I reference the database, row, and column information? It has to be somewhere since the tables were created when the site was created. Otherwise, I can delete the site and try a CLI installation. But it had to create the table somehow!
@@LaravelDaily Working now, thanks!
Hello
Can I download the courses from laravel daily if i subscribe fro one month?
Thank you
Since 2023, most recent courses are TEXT format, not video. So there's nothing to download, really.
i like this approach! but i think this tutorial is not really for beginners, because you're navigating the project files way faster, which is very hard for a complete beginner. just my two cents.
but for intermediate level laravel developers, this is a breathe of fresh air. nice work regardless!
This is the video where you get really off track. Sometimes you speak very quickly. Overall, it feels like I’m watching an amateur-made course. I hope in the future you focus less on profit and more on truly teaching people how to program.
Great video, as always.
I have two questions on your project.
# Database
Concerning the following simplified DB schema:
projects
- user_id
- client_id
tasks
- user_id
- client_id
- project_id
Isn't projects.client_id and tasks.client_id redundant?
With this setup, how do we ensure the two fields are "in sync"?
# Factories
I like your setup, like in project factory you have:
$users = User::pluck('id');
return [
"user_id" => $users-random(),
"name" => fake()->words(2, true),
];
But this means that we have to remember in which order we use the Factories.
You cannot factory-create a Project unless you have created a user first.
If we used
"user_id" => User::factory()
the order in which the factories are called doesn't matter.
But at the same time, it makes our seeders more complex, beause we have to manually feed "sensible" relationships to the factories.
What do you think?
Finally, a comment on the actual topic of the video! :)
DB structure: you're right that you could get the relationship from parent's parent, but then it would be a slower query. In this project, I didn't build anything for them to be in sync but in real project I would do that with observers, probably and not show the dropdown in the form.
With factories, those things are personal preferences.