Weave Code
Tomato Support Laravel Package
tomatophp/tomato-support
tomato-support adds a helpdesk and ticketing system to TomatoPHP admin panels built with Filament. Teams can manage customer tickets, replies, priorities, and statuses from one dashboard, keeping support requests organized in a single, easy-to-use place.
tomato-support is the foundational helper package for the TomatoPHP ecosystem, bundling the shared utilities, traits, and service providers that other Tomato packages rely on. It keeps common logic in one place so your Laravel applications and add-on packages stay consistent, lightweight, and easy to maintain.
- A curated set of global helpers for everyday PHP and Laravel tasks
- Reusable traits for models, resources, and controllers
- Built-in service providers and config publishing for quick setup
- Seamless integration with Laravel and the wider TomatoPHP suite
- Lightweight, dependency-friendly design for package developers
Frequently asked questions about Tomato Support
- What is tomatophp/tomato-support used for in Laravel?
- It is a TomatoPHP package that provides a ticketing and support system with an API for the Tomato admin panel. It also includes helper utilities and support classes for common Laravel admin tasks such as settings, translations, and admin panel integration. Use it when you want to add support tickets and related admin features with less boilerplate.
- How do I install tomatophp/tomato-support with Composer?
- Install the package with Composer using composer require tomatophp/tomato-support. In a TomatoPHP application, complete the usual package setup steps such as publishing configuration or migrations if the package provides them, then run php artisan migrate. Check the repository README for the exact publish tags, service provider registration, and any required admin panel steps.
- Does tomato-support require TomatoPHP or Filament?
- The package is built for the TomatoPHP and Tomato admin ecosystem, so it is intended to be used in a TomatoPHP-style Laravel application. The available summary does not confirm whether Filament is required directly or only through TomatoPHP. Check the package composer.json and README for exact dependencies and Laravel version constraints before installing.
- How does the ticketing and support API work?
- The package provides an API for the ticketing and support system used by the Tomato admin panel. You can use it to manage support tickets from the admin side and from API clients, depending on the routes and middleware the package registers. Inspect the package routes and README for the available endpoints, authentication requirements, and request payloads.
- Can I customize ticket statuses, priorities, or support settings?
- TomatoPHP packages commonly expose settings through configuration files and helper classes, and tomato-support includes support for settings and admin integration. Check the published config and migrations for ticket fields such as status and priority, then extend or override the package classes if you need custom behavior. The exact customization points should be confirmed in the package README and source code.
- Which Laravel versions are supported by tomato-support?
- The exact Laravel version support is not specified in the provided package context. Check the package composer.json for its illuminate/support constraints and required PHP version before installing. Match those constraints to your application's Laravel version, especially if you are upgrading an existing TomatoPHP project.
- How do I test the tomato-support API in a Laravel application?
- Use Laravel's HTTP testing helpers to authenticate as an admin or API user, call the support routes, and assert the JSON responses. Run php artisan route:list to find the exact route names and URIs registered by the package, then use RefreshDatabase so ticket data stays isolated. Review any tests shipped with the package for examples of expected request and response formats.
- Is tomato-support suitable for production use?
- It can be used in production Laravel and TomatoPHP applications, but you should review the package version constraints, test coverage, and API authentication setup first. Pin a known Composer version, run migrations in staging, and confirm that admin and API routes are protected by the middleware you expect. The available context does not include a TPM assessment, so perform your own dependency and security review.
- How is tomato-support different from building a custom ticketing system?
- tomato-support gives you a ready-made ticketing and support API plus helper classes for TomatoPHP admin integration, settings, and translations. A custom system gives you full control over ticket workflows, but you would need to build the models, API, and admin screens yourself. Evaluate the package against your required ticket fields, permissions, and notification workflows before choosing.
- How do I keep tomato-support updated and maintained?
- Use a Composer version constraint that fits your release process, update in a staging environment first, and review the repository commits and releases for changes. Because maintenance activity is not described in the provided context, monitor the GitHub repository for updates and issues. Back up your database and test migrations before updating in production.
Weaver
How can I help you explore Laravel packages today?