Weave Code
Tomato Support Module Laravel Package
tomatophp/tomato-support-module
TomatoPHP Support Module adds a help desk and ticketing layer to Laravel apps, letting teams manage support requests, replies, and statuses from a TomatoPHP admin panel. Lightweight, configurable, and easy to integrate with existing users and permissions.
Ticketing and support system with API for tomato admin
Frequently asked questions about Tomato Support Module
- How do I install tomatophp/tomato-support-module in a Laravel application?
- Install it through Composer with the package name tomatophp/tomato-support-module, then publish its migrations and any config or asset files and run the migrations. Because it is a TomatoPHP module, it is expected to be registered inside a TomatoPHP admin panel installation. Check the repository README for the exact publish tags and any required setup steps.
- Does this package require the TomatoPHP admin panel?
- Yes, it is built as a module for the TomatoPHP admin panel and exposes an API for that admin experience. The ticket, reply, and status management screens are designed for the TomatoPHP admin, so installing it standalone without that ecosystem is not the intended path. If you need a headless ticketing backend, evaluate whether the underlying API and models meet your needs before committing.
- Which Laravel and PHP versions are supported?
- The supported Laravel and PHP ranges are defined in the package's composer.json, so check that file on the repository before installing. TomatoPHP modules generally track recent Laravel releases, but you should confirm compatibility with your application's version and your PHP runtime. If you are on an older Laravel release, verify constraints carefully or test in a staging copy first.
- How does the support module integrate with existing users and permissions?
- The module is described as lightweight, configurable, and easy to integrate with existing users and permissions. In practice, tickets and replies are tied to your application's user records, and access to admin screens is governed by the TomatoPHP permission layer. Confirm the exact relationship and policy setup in the documentation so ticket visibility matches your team structure.
- Is there an API for creating or managing tickets from outside the admin panel?
- The package overview states it includes an API for the Tomato admin, which means ticket data can be reached programmatically rather than only through the dashboard. The precise endpoints, authentication mechanism, and payloads should be confirmed in the README or route definitions. Treat the API as an addition to the admin module, not a fully documented public ticketing API, until you verify it.
- Can I customize ticket statuses, fields, and replies?
- The package is described as configurable, and statuses are managed from the TomatoPHP admin panel, so you can expect to adjust the workflow through configuration and admin screens. For deeper changes such as extra fields or custom reply behavior, review the published migrations and models before altering them. Always re-test after upgrades so your customizations do not conflict with module updates.
- How should I test the support module in my Laravel app?
- Run the package migrations against a dedicated test database and write feature tests that cover creating a ticket, adding a reply, and changing a status. If the repository ships its own tests, run them as part of your pipeline to catch regressions. Keep tests isolated from the admin UI by exercising the models and API endpoints directly.
- Is this package suitable for production use?
- It is part of the TomatoPHP ecosystem and is intended for real admin panels, but production readiness depends on your Laravel version, your review of the code, and the package's release activity. Check recent commits, tagged releases, and open issues on the repository before relying on it. As with any admin module, test upgrades in staging and back up ticket data before changing schemas.
- What alternatives exist to using this ticketing module?
- Alternatives include other Laravel help desk or ticketing packages, a custom build using Laravel notifications, policies, and Eloquent models, or an external SaaS help desk connected through its own API. Choose tomatophp/tomato-support-module if you already run the TomatoPHP admin panel and want tickets managed alongside your other admin resources. If you need a fully independent front end, compare the effort of integrating this module against a custom solution.
- How do I keep the module updated without breaking my ticketing setup?
- Update through Composer, then re-publish any changed migrations or assets only when the release notes indicate it is required. Review the package changelog and diff the config file after upgrades so your custom statuses and settings are preserved. Run your ticket feature tests immediately after updating to confirm replies and status transitions still behave correctly.
Weaver
How can I help you explore Laravel packages today?