How to handle Filament assets (commit or rebuild?)
Hi everyone,
When installing Filament, it automatically adds some assets (JS, CSS, fonts, etc.) to the public/vendor directory.
I was wondering what’s the best practice regarding this:
Should these files be committed to the Git repository, or should they be ignored?
If we choose to ignore them, how can we rebuild them properly in production?
Thanks !
4 Replies
Commit them, they are part of the package (at least that's what we are doing in the team) 🙂
Thanks
I just run
artisan filament:assets in production 🤷🏽
Why commit something that is already versioned.Thanks @Dennis Koch , Yes, that’s actually what I meant — I was wondering whether it’s considered best practice to commit them or to ignore them and rebuild them directly on the server using artisan filament:assets.