Weave Code
Laravel Inbox Laravel Package
ruvelo/laravel-inbox
ruvelo/laravel-inbox provides a lightweight inbox and messaging layer for Laravel applications, with Eloquent-backed conversations and message storage for adding user-to-user or notification-style messaging to existing projects.
The notification inbox Laravel never shipped: a bell, an inbox page and per-user preferences on the database channel.
Frequently asked questions about Laravel Inbox
- What does ruvelo/laravel-inbox add to a Laravel application?
- It adds a notification inbox layer on top of Laravel's database notification channel, including a bell, an inbox page, and per-user notification preferences. It also provides Eloquent-backed conversations and message storage for user-to-user or notification-style messaging. It is intended for existing Laravel projects that need a lightweight inbox without building one from scratch.
- How do I install ruvelo/laravel-inbox with Composer?
- Install it as a normal Composer dependency with composer require ruvelo/laravel-inbox, then follow the repository README for any publishing, migration, or configuration steps. The Laravel Boost integration is opt-in and is added by running php artisan boost:install after upgrading. No Boost installation is required for the core inbox features.
- Which Laravel and PHP versions does ruvelo/laravel-inbox support?
- The provided release notes do not publish a complete support matrix, so check the package's composer.json and README before adopting it. Confirm compatibility against your application's Laravel version, PHP version, and, if used, Laravel Boost version. This is especially important before a broad rollout because the package includes a Blade template for Boost guidelines.
- How does the notification bell and inbox page work in Laravel?
- The package provides a bell and an inbox page backed by Eloquent storage for notifications and messages. It builds on Laravel's database notification channel and adds per-user preferences so users can control what appears in their inbox. You integrate it into an existing Laravel app rather than replacing Laravel's notification system.
- Can ruvelo/laravel-inbox handle user-to-user conversations?
- Yes, the package includes Eloquent-backed conversations and message storage for user-to-user or notification-style messaging. That makes it suitable for adding a simple inbox or direct messaging layer to an existing Laravel project. For complex chat features, evaluate whether its conversation model fits your requirements.
- How do per-user notification preferences work on the database channel?
- Preferences are stored per user and applied to notifications delivered through Laravel's database channel. This lets each user control which notifications land in their inbox without changing the underlying notification classes. Review the package's models and configuration to confirm how preference keys map to your notification types.
- Do I need Laravel Boost to use ruvelo/laravel-inbox?
- No. Laravel Boost is optional developer tooling for AI coding agents; the inbox, bell, preferences, conversations, and messages work without it. Version 1.1.0 adds AI-agent guidance under resources/boost/guidelines/ and an opt-in boost:install entry point. Teams not using Boost can upgrade safely but receive no benefit from that specific feature.
- What does php artisan boost:install do in ruvelo/laravel-inbox?
- It is the opt-in entry point for installing the package's Laravel Boost AI-agent guidelines. The release notes indicate it integrates with Boost rather than acting as a runtime dependency, but they do not fully document whether it publishes, merges, or only prints guidelines. Test it in a sandbox and review the resulting guidelines before committing them.
- Is ruvelo/laravel-inbox v1.1.0 a breaking change?
- Based on the provided notes, v1.1.0 is additive and non-breaking. Existing consumers should upgrade through the normal composer update path and pin the version according to their dependency policy. Teams using Boost should run boost:install after upgrading and review any generated guidelines for conflicts.
- How should I test and roll out ruvelo/laravel-inbox in production?
- Validate the package against your Laravel, PHP, and Laravel Boost versions in a staging or sandbox application first. Check that boost:install is idempotent, does not overwrite custom guidelines, and that its Blade template renders correctly on your supported Laravel versions. Roll out to a small pilot team, decide whether generated guidelines are committed, and monitor AI-agent output and developer feedback.
Weaver
How can I help you explore Laravel packages today?