Weave Code
Tomato Notifications Module Laravel Package
tomatophp/tomato-notifications-module
A Laravel notifications module for TomatoPHP apps that centralizes notification management, delivery, and templates, with admin-panel integration for configuring and tracking notifications without building the infrastructure from scratch.
Laravel Notifications Channel with GUI to send notifications with templates
Frequently asked questions about Tomato Notifications Module
- How do I install tomatophp/tomato-notifications-module in Laravel?
- Install it with Composer, then publish the package config and migrations and run them in a non-production environment first. The package is designed for TomatoPHP panels and relies on Laravel package auto-discovery plus Filament admin resources. Before installing, confirm the declared PHP, Laravel, and Filament constraints match your application.
- Does this package work with a vanilla Laravel app or only TomatoPHP?
- It is a strong fit only when your application is already a TomatoPHP panel, where you get pre-built Filament resources, migrations, and notification-management screens. In a plain Laravel app it mostly wraps native database notifications, notifiable traits, and mail/database channels while adding a Filament/TomatoPHP dependency footprint. For vanilla Laravel, use the framework's native notification system directly.
- Which Laravel and Filament versions are supported?
- The package does not document a clear compatibility matrix in the overview, so check composer.json for constraints on PHP, laravel/framework, filament/filament, and tomatophp core packages. Filament v3 to v4 is a hard compatibility axis; a module pinned to the wrong major will not co-install. Verify the constraints before scheduling any integration work.
- What changed in version 1.0.2 of tomato-notifications-module?
- The release notes for v1.0.1 to v1.0.2 contain only a compare link, with no enumerated commits, changelog entries, or stated fix. That makes the patch bump an opaque change to code that runs in your notification path, where silent failures are costly. Treat v1.0.2 as a new, unvetted artifact until you diff it or get clarification from the maintainer.
- Does this module replace Laravel's native notification system?
- It layers Filament resources, migrations, and notification-management UI over Laravel's native notification subsystem rather than replacing the framework primitives. It likely wraps database notifications, notifiable traits, and mail/database channels. Confirm with the maintainer whether it owns templates and user preferences or only provides transport and UI.
- What database tables and migrations does this package add?
- The exact migration footprint is not documented in the provided overview; expect at least notification-related tables and possibly template or preference tables. Publish the migrations and diff them against your existing schema before running anything, because table-name or column collisions are the most likely integration failure. Plan an explicit rollback with migrate:rollback plus documented table or column removal rather than trusting down() methods you have not read.
- Can I use tomato-notifications-module with Filament v4?
- Only if the package's composer.json allows Filament v4; the TomatoPHP ecosystem moves on Filament major versions and v3 to v4 is a hard compatibility boundary. A module pinned to Filament v3 will not co-install with a v4 panel. Check the constraint and pin an exact package version instead of floating on a caret range.
- How do I publish the config and migrations for this Laravel notifications module?
- Use Laravel's standard vendor:publish flow for the package service provider to publish config and migration files, then inspect the generated files before migrating. Install into a disposable branch or non-production environment first and diff the migration set against your schema. If you adopt it, sequence the work as publish, inspect, migrate, then backfill only if you need historical notification records imported.
- Is this notifications module production ready, and what about tests and CI?
- The evaluation notes unknown test coverage and CI signals, a single maintainer, and unclear license and stewardship terms, so it should not be treated as a validated release without checks. Run your existing test suite with the package installed and review its migrations and notification path in a scoped pilot. Pin an exact version and avoid committing to adoption until compatibility and release cadence are verified.
- What are the alternatives to tomato-notifications-module for Laravel notifications?
- The primary alternative is Laravel's native notification system with database notifications, mail channels, and notifiable traits, which avoids the extra Filament and TomatoPHP footprint. If you need admin screens, build a small Filament resource over native notifications or use other TomatoPHP modules that match your panel version. Revisit this package only if you are already on a compatible TomatoPHP panel and want its pre-built template and tracking UI.
Weaver
How can I help you explore Laravel packages today?