Weave Code
Tomato Pms Module Laravel Package
tomatophp/tomato-pms-module
Laravel module for TomatoPHP that adds a lightweight project management system to your admin panel. Organize projects, tasks, teams, and progress in one place, with a consistent admin interface and Composer-based installation.
Project Management System for TomatoPHP Echo System
Frequently asked questions about Tomato Pms Module
- How do I install tomatophp/tomato-pms-module in a Laravel application?
- Install it with Composer by requiring tomatophp/tomato-pms-module; Laravel package auto-discovery registers the service provider and Filament panel plugin automatically. The host application must already run the TomatoPHP admin panel with Filament, since this is a panel module rather than a standalone library. After installing, run the package migrations and confirm the PMS resources appear in your admin panel navigation.
- Can I use this package in a plain Laravel app without Filament or TomatoPHP?
- No. tomatophp/tomato-pms-module is a domain module for the TomatoPHP ecosystem that plugs into a Filament admin panel, so it assumes the panel, Livewire, and the surrounding Tomato modules are already present. Adding it to a bare Laravel application will not give you a usable project management system. If you are not on TomatoPHP, look for a standalone Laravel PMS package or build your own resources instead.
- Which Laravel, PHP, and Filament versions does this module support?
- The module targets Laravel 10 or 11, PHP 8.1+, Livewire 3, and Filament 3 alongside the TomatoPHP admin panel, but the changelog does not state explicit version constraints. Read the require block in composer.json for the exact pins before installing, because minor releases sometimes tighten a Filament or Laravel constraint. Filament's major-version cadence is the most likely source of future breakage.
- What does the register generate artisan command do in v1.0.1?
- Version 1.0.1 adds an opt-in Artisan command that scaffolds a module registration entry, following TomatoPHP's convention of self-registering modules. It does not execute on install or boot, so it has no effect on existing consumers until you deliberately run it. The change is purely additive with no schema, config-key, or contract changes.
- Is the register generate command idempotent, and will it overwrite my existing registration file?
- The v1.0.1 changelog is a single line and does not document whether the command fails safely or mutates an existing registration or config file. Before using it on a real project, run it against a sandbox copy of the application and diff the output. Treat inspecting its behavior as a required manual review step rather than an assumption.
- Does the module ship migrations, and will its tables collide with other TomatoPHP modules?
- The package includes migrations for its project management entities, but table prefixing and namespacing relative to sibling Tomato modules are not verified in the release notes. Review the migration files and check table names against other modules installed in the same database. Running migrations in a staging environment first is the safest way to catch collisions.
- Does tomatophp/tomato-pms-module support multi-tenancy or team-based scoping?
- The module organizes projects, tasks, and teams in a single admin panel, but multi-tenancy and tenant-scoped data isolation are not documented. Until proven otherwise, assume it is designed for single-tenant usage. If you need strict tenant isolation, plan additional scoping work or choose a package built for that requirement.
- How do I upgrade from v1.0.0 to v1.0.1?
- The upgrade is additive: bump your Composer constraint to ^1.0.1, run composer update tomatophp/tomato-pms-module, and confirm the lockfile resolves cleanly. Diff the composer.json require block between the two tags, since a minor release could narrow a Filament or Laravel constraint and break an existing lockfile. There is no data migration, config rename, or published-asset change, and rollback is simply re-pinning version 1.0.0.
- Is the package actively tested and maintained, and is there CI coverage?
- The project is a v1.0.x, single-maintainer package with low release churn, a one-line changelog, and no test evidence linked in this release. That does not mean it is broken, but it does mean you should not rely on upstream test coverage for confidence. Run your own smoke tests across the PMS Filament resources, including list, create, and edit screens, plus your existing application suite.
- When should I choose this module over an alternative project management package?
- Choose it when your application already runs the TomatoPHP admin panel and Filament, because integration cost is low and the interface stays consistent with your other modules. For a cold Laravel application, a standalone PMS library, a dedicated Filament plugin, or an external project management tool is usually a better fit than adopting an entire ecosystem for one module. Compare migration naming, tenancy support, and maintenance activity before committing.
Weaver
How can I help you explore Laravel packages today?