When running Horizon on a non-dev environment
@dzanfardino you'll want to publish the assets again (looking for a manifest.js file) and hard refresh the page.
php artisan vendor:publish --provider="Laravel\Horizon\HorizonServiceProvider"
Yes re-publish the files and make sure the mix-manifest is correctly pushed to your server.
why is this closed? is this step documented somehwere I didn't find @themsaid ? should we at least put something elsewhere so installing horizon doesn't involve googling and finding this issue?
@acidjazz
It is in fact documented at https://laravel.com/docs/5.5/horizon#installation
thanks @wells i wonder if this could be run w/in composer.json or as a suggested command?
do people commit their public/vendor directory to Github? currently I have it ignored, and I usually include something in my front end build script to copy stuff in there.
In case anyone is still struggling with this, I resolved the issue by adjusting my base .gitignore file to have
/vendor/
instead of
vendor/
The first version was causing my public/vendor folder to be ignored and not deployed.
Yes this should be noted on the vendor ignore path somewhere...
Most helpful comment
In case anyone is still struggling with this, I resolved the issue by adjusting my base
.gitignorefile to haveinstead of
The first version was causing my
public/vendorfolder to be ignored and not deployed.