Log1x
Issue after update to 3.1
i dont think the filament upgrade package for v2 to v3 mentioned in the docs does it automatically, but otherwise,
filament:upgrade
should be in post-autoload-dump
as it has changes often and needs to publish its assets in most cases.
you can see in the filament:install
command that it gets added here: https://github.com/filamentphp/filament/blob/49be4992a5c5df58d9702de5817a6a7fbf8e1aef/packages/support/src/Commands/InstallCommand.php#L156-L163
which is reflected in my starter: https://github.com/Log1x/filament-starter/blob/main/composer.json#L5054 replies
`php artisan icons:cache` required but not documented?
for what it's worth, I have a filament dashboard with 50k software, 400k files, 1.5 million file versions, and like 100k threats and have blade icons literally plastered everywhere and completely forgot about ever thinking about caching it til this thread. i've had 0 performance issues and its on a $10 droplet. this site also has a full frontend that also uses blade icons so... ive never had to think about performance once. its always been ⚡
78 replies
Login in production
DigitalOcean alongside something like https://forge.laravel.com/ or if you need more than just Laravel (e.g. WordPress), I like to use https://runcloud.io/
9 replies
Sort resource by relationship count – exception when empty
yeah & using https://filamentphp.com/docs/3.x/tables/columns/relationships#counting-relationships for the column. i assume ill have to take a different approach
5 replies