When you create the filament resource, you can add --generate and it will add the model's fields to the table and forms, saving you a lot of manual creating those. You just have to modify them if you want something other than the defaults. In your case, that would be php artisan make:filament-resource Note --generate
Filament is the perfect complement to Livewire, no need to worry about Javascript, now with Filament Form Build and Actions, no need to worry about HTML/Styling code. Unless there is a very custom need and every element of Filament always has a custom element that can use a blade view to add any custom HTML code to it.
one tip: instead of showing your viewers to skip 'starring the repo', you should inform them that you have already done that(which I hope you have) and that's why you're skipping here or any suitable reason, which will not impact the maintainers. Love your videos, keep'em coming
My experience. I love Filament. I have a production project running on Laravel 9 and Filament 2. A lot a new features are available in Filament 3, but when we decided to upgrade the project it was not possible. We need to decide if we continue on Laravel 2 and making our own custom code or start over in Filament 3.
I'm really on the fence with filament. I recently started a bigger project that will be with me for at least 10 years and really could use the help of filament but I'm also too scared to find myself in a bad situation with another mayor update in the future. I do see the benefits and absolutely would love to use it. But I also remember, that the update from the previous version to the current one meant a lot of work across the application. Once you decide to rely on a big package like this one, you're kind of stuck on a specific Laravel version as long as there (1.) isn't a compatible filament version and (2.) you didn't ship in the work to update your app.
It's a tradeoff, yes, but same with Laravel and any package, no guarantee that in the future the updates would be easy. Not sure what else Filament creators can do to "convince" you to trust them.
I don't think there's anything specific needed for filament, to be honest. It's a typical Laravel project. Which part of deployment is tricky to you? Also, from what I know, most developers use nginx and not apache
Love your content, could you please make a video about Laravel waf and how you secure the project from routing to accessing files within the server. Have a beautiful day ❤️
This might be just me, but I intentionally try to stay away from Filament. It is a new DSL. If I can, I rather learn things that I can transfer across domains. It might be good for quickly putting together a MVP, but I doubt its customizability. Also, I'm a Laravel novice, so there's that.
thanks for making this videos, what do you think between Filament and Laravel Nova in terms of development complexity, time and flexibility for build mid-size project?
why is your filament project loading fast and no delay. while when I first created it, it was slow. when moving menus it can take 2-5 seconds, please explain
I love Filament and all but how cool would it be if there was something similar but built with Vue.js or React and allows for CSR instead of SSR? I mean, anything behind a login screen doesn't need SEO so seems like an unnecessary load on the server.
hey Povilas, I have worked with Laravel Nova, is it safe to say that filament is a laravel nova alternative with possibility to add the features to your app views not only admin dashboard ?
You can use Filament as a separate adminpanel, and continue the main page with whatever other technology you want. But inside Filament yes, it's TALL stack. Technically you don't need Livewire/Alpine knowledge to use Filament, but if you get to more complex customizations, then you'll need those.
Well, the biggest difference for people is free vs paid product. Then, the stack is different: Filament is TALL, Nova is VILT. Finally, in terms of flexibility and ease of use, people on Reddit recently preferred Filament: www.reddit.com/r/laravel/comments/17xhoyl/what_can_filament_do_more_than_nova/
Why I always feel thats Filamentphp is slow compared with other laravel stacks , is this also existing in real server hosting or maybe my pc is less efficiency to load filament
@@LaravelDaily A simple example: When I click on a button, a loading pattern appears, even if it appears for a short time, but it appears... Also, moving from page to page takes some time. Why? I think loading css and js files every time might be the reason for this? Is using filament considered practical in large real projects? I would like an answer please
That "takes some time" is really hard to measure, maybe it's your local situation? I've heard the idea that Livewire is bad for performance on bigger projects but yet to experience it myself
@@Mr.Error__ The loading indicator just provides visual feedback for the processing state obviously. And depending on what the DB runs on, e.g. virtual machine, locally hosted, or whatever and of course the complexity and load of data, it can load more or less. Try the Laravel Debugbar and check the requests, resources etc. and maybe you'll be able to find out why it's taking so "long". But if it's just the loading itself that annoys you, you're better off with a SPA and self regulated / accumulated requests that don't split up as much.
@@LaravelDaily do you feel the laravel ecosystem has gotten a bit spoiled for choice lately? many plugins, many ways of doing the same thing basically with different level of flexibility. But for new people they might be like "what am i supossed to learn"
This will change as the plugin base grows. But apart from that it's single payments as from what I've seen. So as long as we don't get subscription based plugins, I am totally fine with it, as long as the plugins are reasonably priced. (Remember est. worktime * hourly pay >= plugin price ? Worth it!)
![แข่งเพิ่มน้ำหนักใน 24 ชั่วโมง!! [Ver 2025]](http://i.ytimg.com/vi/20xn0g6k-ec/mqdefault.jpg)
When you create the filament resource, you can add --generate and it will add the model's fields to the table and forms, saving you a lot of manual creating those. You just have to modify them if you want something other than the defaults. In your case, that would be php artisan make:filament-resource Note --generate
Filament is the perfect complement to Livewire, no need to worry about Javascript, now with Filament Form Build and Actions, no need to worry about HTML/Styling code.
Unless there is a very custom need and every element of Filament always has a custom element that can use a blade view to add any custom HTML code to it.
one tip: instead of showing your viewers to skip 'starring the repo', you should inform them that you have already done that(which I hope you have) and that's why you're skipping here or any suitable reason, which will not impact the maintainers.
Love your videos, keep'em coming
Thank you for the easy & concise intro 👍
My experience. I love Filament. I have a production project running on Laravel 9 and Filament 2. A lot a new features are available in Filament 3, but when we decided to upgrade the project it was not possible. We need to decide if we continue on Laravel 2 and making our own custom code or start over in Filament 3.
I'm really on the fence with filament. I recently started a bigger project that will be with me for at least 10 years and really could use the help of filament but I'm also too scared to find myself in a bad situation with another mayor update in the future.
I do see the benefits and absolutely would love to use it. But I also remember, that the update from the previous version to the current one meant a lot of work across the application. Once you decide to rely on a big package like this one, you're kind of stuck on a specific Laravel version as long as there (1.) isn't a compatible filament version and
(2.) you didn't ship in the work to update your app.
It's a tradeoff, yes, but same with Laravel and any package, no guarantee that in the future the updates would be easy.
Not sure what else Filament creators can do to "convince" you to trust them.
Actually I haven't tried yet, but it seems really amy, I must try
Good to see laravel getting on the same page as django
a few pages ahead you mean
Django that slow slop 😂
great. I will use filament in my next project. thanks f or the nice demo
Cool ! I really should try this . Thanks, sir
Thanks, seems so awsome❤
Error: in using Repeater for relations hasmany , in edit it shows only first record
Sorry it's hard to comment and debug your issue in a comment, without looking at the code.
Thank you for sharing. Please try to make a video for deploy Laravel with filament on server, most developer not know and they use apache server.
I don't use Apache myself, I use Nginx, so can't shoot a video about Apache, sorry
@@LaravelDaily I mean most developer use apache server. Please make a video on nginx with Laravel & filament
I don't think there's anything specific needed for filament, to be honest. It's a typical Laravel project.
Which part of deployment is tricky to you?
Also, from what I know, most developers use nginx and not apache
Love your content, could you please make a video about Laravel waf and how you secure the project from routing to accessing files within the server.
Have a beautiful day ❤️
I haven't used a waf in Laravel so can't make a video about it
@@LaravelDaily Thank you anyway, keep the good content ❤️
Wow!
please make some video about customizing styles, for example, I want buttons with less pading or compact table. and different colors.
I have quite a lot of such videos on my FilamentDaily channel. Also a lot of it is in the docs.
It would be nice to have compact tables.
Qeustion mr. Korop, can laravel manage something like booking system. Think of it as a ticket management system
Yes why not? It's not about Laravel, it's about the skill of developer who writes that Laravel code.
I'm a evaluating my options for a new project, it's a CRM, what do you think? my other choice would be to use inertia with a custom admin theme.
It's very individual, impossible to answer. But there are CRM systems with Filament, google it
@@LaravelDaily I will, thanks for the quick reply :)
This might be just me, but I intentionally try to stay away from Filament. It is a new DSL. If I can, I rather learn things that I can transfer across domains. It might be good for quickly putting together a MVP, but I doubt its customizability.
Also, I'm a Laravel novice, so there's that.
thanks for making this videos, what do you think between Filament and Laravel Nova in terms of development complexity, time and flexibility for build mid-size project?
I haven't used Nova in production so can't compare. But search on Reddit there were a few posts with many comments
Is it Filament suitable for smaller/simpler alternative to shopify? Multi-tenant separate database?
Not sure, haven't tried that exact use case
why is your filament project loading fast and no delay. while when I first created it, it was slow. when moving menus it can take 2-5 seconds, please explain
I don't know, I can't debug the project in your case on your server.
I don't use debugbar
I love Filament and all but how cool would it be if there was something similar but built with Vue.js or React and allows for CSR instead of SSR? I mean, anything behind a login screen doesn't need SEO so seems like an unnecessary load on the server.
*similar and open-source (hence not Nova)
You can always be the first to do it! :)
@@LaravelDaily I'll leave it to developers smarter than me to figure this one out :)
hey Povilas, I have worked with Laravel Nova, is it safe to say that filament is a laravel nova alternative with possibility to add the features to your app views not only admin dashboard ?
Yes, absolutely right
Can i use my already existing login form/route instead of the one filament registered?
You can technically, but that would require some custom work to make it function properly.
Do you have an example of laravel filament and Sql Server?
No I don't use SQL server, sorry
Is it only for administrating tables or can you generate public views with it also?
You can have public views as Livewire components, yes
I wasn’t aware of filament and ended up buying nova, does nova provide something filament doesn’t?
They are comparable but different stack, search on Reddit filament vs nova, there are a lot of discussions with pros and cons.
Is the TALL stack mandatory to use Filament? If I dont use alphine or livewire, I can't use Filament?
You can use Filament as a separate adminpanel, and continue the main page with whatever other technology you want.
But inside Filament yes, it's TALL stack. Technically you don't need Livewire/Alpine knowledge to use Filament, but if you get to more complex customizations, then you'll need those.
@@LaravelDaily Noted. Thank you for the reply
good
How does Filament compare to Laravel Nova?
Well, the biggest difference for people is free vs paid product.
Then, the stack is different: Filament is TALL, Nova is VILT.
Finally, in terms of flexibility and ease of use, people on Reddit recently preferred Filament: www.reddit.com/r/laravel/comments/17xhoyl/what_can_filament_do_more_than_nova/
Why I always feel thats Filamentphp is slow compared with other laravel stacks , is this also existing in real server hosting or maybe my pc is less efficiency to load filament
Do you have any calculations to prove it's slow? What exactly is slow? If you provide videos or console measurements, I could try to explain or debug.
@@LaravelDaily
A simple example: When I click on a button, a loading pattern appears, even if it appears for a short time, but it appears... Also, moving from page to page takes some time. Why? I think loading css and js files every time might be the reason for this? Is using filament considered practical in large real projects? I would like an answer please
That "takes some time" is really hard to measure, maybe it's your local situation?
I've heard the idea that Livewire is bad for performance on bigger projects but yet to experience it myself
@@Mr.Error__ The loading indicator just provides visual feedback for the processing state obviously. And depending on what the DB runs on, e.g. virtual machine, locally hosted, or whatever and of course the complexity and load of data, it can load more or less. Try the Laravel Debugbar and check the requests, resources etc. and maybe you'll be able to find out why it's taking so "long".
But if it's just the loading itself that annoys you, you're better off with a SPA and self regulated / accumulated requests that don't split up as much.
fillament charges a lot of money for plugins that can be done pretty fast
I don't see a problem here: if you know how to do something pretty fast, then do it yourself and don't pay for the plugins :)
@@LaravelDaily do you feel the laravel ecosystem has gotten a bit spoiled for choice lately? many plugins, many ways of doing the same thing basically with different level of flexibility. But for new people they might be like "what am i supossed to learn"
This will change as the plugin base grows. But apart from that it's single payments as from what I've seen. So as long as we don't get subscription based plugins, I am totally fine with it, as long as the plugins are reasonably priced. (Remember est. worktime * hourly pay >= plugin price ? Worth it!)
Personally, I prefer many options over one option.
For new people, I'm trying to shoot videos to un-confuse them :)
Is it free?
Yes.
Using blade in 2024.. facepalm