Weave Code
Laravel Laravel Package
belltastic/laravel
Belltastic for Laravel provides a clean integration with the Belltastic notification service, letting Laravel apps send and manage notifications through a familiar API. Includes configuration, notification channel support, and straightforward setup.
Laravel helper package to easily send Belltastic Notifications
Frequently asked questions about Laravel
- How do I install and configure belltastic/laravel?
- Install it with composer require belltastic/laravel, pinning 0.4.1 exactly while the package is pre-1.0. Laravel package discovery should register the service provider automatically, and if the package ships a config file you can publish it to set your Belltastic API credentials. Check the published config or package source for the exact environment variable names, then verify the provider boots in a throwaway branch before rolling it out.
- Does belltastic/laravel support Laravel 10 or Laravel 11?
- The only confirmed framework compatibility signal is Laravel 9, added in 0.4.1. Laravel 10 and 11 support is unverified, so treat those versions as out of scope until a release or composer.json explicitly declares them. Check the package's composer.json require constraints and recent tags before adopting it on a newer Laravel app.
- What PHP version does belltastic/laravel require?
- The release notes do not state a PHP version constraint, so the authoritative source is the require block in the package's composer.json. Confirm the constraint matches your runtime, especially if you are on PHP 8.0 or 8.1, and lock that PHP version in CI. Do not assume compatibility from the package working on a maintainer's machine.
- How do I send an in-app notification with Belltastic in Laravel?
- Belltastic provides a fluent API for creating and sending in-app notifications, and it also integrates with Laravel's notification system through a channel. You can either call the fluent API directly from your application code or define a Laravel notification class that routes through Belltastic. Use recipient targeting to address the right user, and confirm the exact class and method names in the package documentation for 0.4.1.
- Does belltastic/laravel track read and unread notifications per user?
- Yes. The package provides per-user read/unread tracking and notification management, which is the core of a notification bell or feed. That state is managed through the Belltastic service rather than requiring you to build your own read receipts table. Check the API surface in 0.4.1 for the exact methods used to mark notifications as read.
- Can I queue Belltastic notifications with Laravel queues?
- The package is described as integrating with Laravel Notifications and queues, so if you send through a notification class you can implement ShouldQueue as you would for any other channel. That keeps API calls off the request cycle and lets your existing queue workers handle retries. Verify queue behavior in a staging environment, since 0.4.1 is pre-1.0 and the integration details may change.
- Does belltastic/laravel ship database migrations?
- That is not confirmed in the release information provided, and whether the package ships migrations or touches your database is a key integration question. Inspect the package source and service provider for migration loading, publishable assets, or schema assumptions before installing. Test the install in a throwaway Laravel 9 branch so any schema dependency shows up before it reaches a shared environment.
- How do I test Belltastic notifications without calling the real API?
- The release information does not confirm a built-in fake or test helper, so plan to isolate the package behind a thin internal adapter or interface. If the package uses Laravel's HTTP client, you can lean on HTTP fake assertions; otherwise inject a test double at your adapter boundary. Keep those tests in CI so a future 0.x upgrade that changes the API is caught quickly.
- Is belltastic/laravel 0.4.1 safe to use in production?
- It is pre-1.0, so treat it as an enabling release rather than a stable dependency: pin 0.4.1 exactly, read every 0.x changelog, and avoid caret ranges that could drift into 0.5 without review. Start with a spike in a throwaway Laravel 9 branch, wrap the package behind an adapter, and pilot it on one non-critical surface. Promote it to a primary workflow only after a 1.0 release or a sustained run of stable 0.x patches.
- What are the alternatives to belltastic/laravel for in-app notifications?
- Laravel's built-in database notification channel plus a small read/unread table covers many in-app notification needs without an external service. Other hosted notification services and custom feed implementations are alternatives if you need cross-channel delivery or a managed bell UI. Choose Belltastic if you want a hosted in-app notification feed with read state and recipient targeting rather than maintaining that infrastructure yourself.
Weaver
How can I help you explore Laravel packages today?