Weave Code
Tomato Notifications Laravel Package
tomatophp/tomato-notifications
tomatophp/tomato-notifications adds a ready-made notification layer to TomatoPHP and Laravel apps, with database-backed alerts, Filament-friendly UI hooks, and configurable channels to keep users informed.
Laravel Notifications Channel with GUI to send notifications with templates
Frequently asked questions about Tomato Notifications
- What does tomatophp/tomato-notifications actually do?
- It is an ecosystem add-on for TomatoPHP and Laravel apps that contributes three things over stock Laravel: a persisted notification template model, a Filament CRUD and send resource, and a channel class that hooks into Laravel's native Notification system. Delivery, queuing, localization, and retries all remain Laravel core, so it is not a full notification platform. Treat it as a narrow buy-vs-build shortcut for an admin-composed template layer behind an in-app inbox.
- How do I install tomatophp/tomato-notifications?
- Installation is mechanically trivial: composer require the package, the service provider is auto-discovered, then you publish the config and migrations. Before committing further, spend about half a day reading composer.json and the provider to confirm the illuminate/* version range, the required Filament major, and whether tomato-admin, tomato-settings, and tomato-roles are hard requirements or soft suggestions. A clean composer install is evidence of a clean install only, not of a validated integration.
- Which Laravel and PHP versions are supported?
- There is no verified support matrix; the package has 1 star, 0 dependents, and its last release was mid-2024. Check the illuminate/* constraint in composer.json directly, since the realistic high-fit target is PHP 8.x with Laravel 10 or 11, Livewire, Filament 3, and the Tomato admin suite already in production. Pin the exact version and treat every bump as a reviewed change.
- Do I need Filament and the Tomato admin suite to use it?
- The GUI ships as a Filament resource, so the full out-of-the-box value assumes Filament 3 and likely the Tomato admin suite. On any other stack the dependency cost is disproportionate: a full Filament admin tree pulled in for one model, one resolver, and one channel class. The recommended path outside Tomato is to fork under MIT, keep the template model, migration, resolver, and channel, and drop the Filament resource.
- Is the template rendering safe, or is there a code execution risk?
- This is a blocking question: if templates compile through Blade::render or eval, then template-edit permission effectively becomes code-execution permission. Verify the renderer implementation before adopting, and prefer restricted variable substitution over arbitrary template evaluation. That reframes the admin GUI value proposition as a security review item rather than a pure convenience win.
- How are queued notifications handled if a template is edited mid-flight?
- Determine whether templates are snapshotted into the queued job payload at dispatch time or resolved at execution time. If they resolve at execution, editing or deleting a template while jobs are in flight changes what actually ships to users. Snapshotting is the safer design and should be confirmed in the source before you rely on it.
- Will it collide with Laravel's own notifications table or my existing template tables?
- Possibly, so review the published migrations for table names and prefixes before running them against a real database. Check for collisions with Laravel's notifications table and any notification template tables you already own. Plan the schema and migration order in an existing application rather than discovering conflicts after the fact.
- What happens when a template variable is missing or a channel fails?
- It is unclear whether variable validation is enforced at save time or whether a missing placeholder fails at send time. Include a save-and-send test with missing variables in your spike. Also check whether channel failures are surfaced to your error tracking or caught and logged silently, since silent failures are the harder production problem.
- Can I use the template model headlessly without installing the Filament UI?
- That is unproven; no integration other than the author's own has been validated, so headless usage and multi-tenant or per-locale template support should be treated as open questions. The practical route is to fork the package, keep the model, migration, resolver, and channel, and expose templates through your own admin surface. MIT licensing makes forking legally clean, so lock-in is bounded to engineering labor rather than legal exposure.
- Is it production-ready, or should I build this in-house instead?
- Maintenance risk dominates here: a single-maintainer organization publishing many interdependent packages, no visible security-disclosure process, no evidence of a test suite, and no upgrade cadence. The decision is a narrow buy-vs-build one, so get an in-house estimate in the same window as your spike. A notification_templates table, a cached resolver, and a channel over a whitelisted variable set is roughly 150 to 250 lines, which is the real threshold to compare against.
Weaver
How can I help you explore Laravel packages today?