We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
1.2.4
11.16.0
8.2.20
3.5.4
No response
Following the installation guide, which advises to run vendor:publish to publish the Pulse config and migrations did not work for me:
$ php artisan vendor:publish --provider='Laravel\Pulse\PulseServiceProvider' INFO No publishable resources for tag [].
Only publishing with a --tag did put the relevant migration in place:
--tag
$ php artisan vendor:publish --tag="pulse-migrations" INFO Publishing [pulse-migrations] assets. Copying directory [vendor/laravel/pulse/database/migrations] to [database/migrations] ....................................................... DONE
See description above.
The text was updated successfully, but these errors were encountered:
Hi, @avioli, thanks for reporting this.
I just ran the installation against a clean install and all seems to be working.
I wonder if this has something to do with you using single quotes or if there is something weird going on with the escape characters.
What terminal / shell are you using?
Sorry, something went wrong.
Closing this issue because it's inactive, already solved, old or not relevant anymore. Feel to open up a new issue if you're still experiencing this.
timacdonald
No branches or pull requests
Pulse Version
1.2.4
Laravel Version
11.16.0
PHP Version
8.2.20
Livewire Version
3.5.4
Database Driver & Version
No response
Description
Following the installation guide, which advises to run vendor:publish to publish the Pulse config and migrations did not work for me:
Only publishing with a
--tag
did put the relevant migration in place:Steps To Reproduce
See description above.
The text was updated successfully, but these errors were encountered: