Closed tabacitu closed 1 year ago
Actually this might not be needed. Maybe there's a bug in basset:fresh
and that's what we actually need to fix - https://github.com/Laravel-Backpack/basset/issues/70
In our demo:
basset:fresh
works incorrectly`basset:fresh
actually does the jobWhich is why the fix has always been to re-deply or re-run basset:fresh
.
In the meantime, I've made our deploy script do php artisan basset:clear && php artisan basset:cache
which should fix this problem. So I'll close this and reopen if I'm wrong.
Sometimes in our demo, basset URLs do not load what they're supposed to - see https://github.com/Laravel-Backpack/demo/issues/552 for more info.
I tested multiple things, and fixes it is running
php artisan basset:fresh
. So maybe we should do this after eachdb:fresh
? 🤷♂️My only problem with this is that... I don't understand why. Why does
db:fresh
break assets? And does it really? Because on localhostdb:fresh
does NOT break stuff for me. So... this fixes it... and applies the fix every hour... so it increases the changes that people don't see our demo broken... but... why?