Weave Code
Tomato Freelancers Laravel Package
tomatophp/tomato-freelancers
Tomato Freelancers is a Laravel package for managing freelancers, clients, and projects inside the Tomato admin ecosystem, with ready-made CRUD resources, database migrations, and configurable workflows for hiring and tracking contract work.
Freelancer Gate for Tomato PMS
Frequently asked questions about Tomato Freelancers
- What is Tomato Freelancers and what does it do?
- Tomato Freelancers is a Laravel package published as tomatophp/tomato-freelancers that manages freelancers, clients, and projects inside the Tomato admin ecosystem. It ships with ready-made CRUD resources, database migrations, and configurable workflows for hiring and tracking contract work. It is a domain module for the TomatoPHP/Filament world rather than a framework-agnostic library, so it fits best when you already run a Tomato or Filament admin panel.
- How do I install tomatophp/tomato-freelancers in a Laravel application?
- Installation is the standard Composer path: require tomatophp/tomato-freelancers and then run your migrations. Because the package auto-registers a service provider and ships migrations, review what it registers before running it against an existing database. The published documentation is thin at 0.0.1, so confirm the exact install steps with the maintainer or the repository README before committing.
- Do I need Filament or a TomatoPHP admin panel to use this package?
- Almost certainly yes. The package is published under the tomatophp vendor namespace and its CRUD resources are built for the Tomato admin ecosystem, which is Filament-based. That makes it a poor fit for headless APIs, non-Filament admin surfaces, or service-oriented architectures where domain logic should live outside form schemas and resource classes. If you are not already running TomatoPHP or Filament, evaluate the coupling carefully before adopting it.
- Which Laravel and PHP versions does tomato-freelancers support?
- The supported Laravel and PHP ranges are not documented in the 0.0.1 release, which contains no changelog body or composer.json constraint details. TomatoPHP packages commonly pull Filament and related UI dependencies transitively, and those can silently constrain your admin-panel upgrade path. Ask the maintainer directly, or inspect the composer.json require block, before adding it to a project on a specific Laravel version.
- Does Tomato Freelancers create its own database tables, and can I publish the migrations?
- The package ships database migrations, but the migration inventory is not published with the 0.0.1 tag. Freelancer and payout domains are schema-heavy, so you need to confirm which tables the package owns versus which remain yours. Migration ownership is expensive to reverse once data lives in tables you did not design, so verify publishability and customization options first.
- Is version 0.0.1 stable enough to use in production?
- Treat 0.0.1 as pre-alpha. Semantic versioning permits breaking changes in any 0.0.x bump, so pinning to ^0.0.1 gives you no compatibility guarantee, and there is no published API contract to code against. Risk here is driven by information scarcity rather than an identified defect, so a production commitment should wait until the API surface, dependency constraints, and release cadence are documented.
- Can I use Tomato Freelancers to build a headless API or a non-Filament admin?
- It is a poor fit for that use case. Admin-UI-coupled packages tend to bury domain logic in resource classes and form schemas rather than exposing a reusable service layer you can call from controllers or jobs. For an API-first product, you would likely end up reimplementing the business rules elsewhere, which defeats the point of adopting the package.
- Does tomato-freelancers include authorization policies or gates for freelancers and clients?
- An authorization layer is not confirmed in the published material. Filament-based modules often rely on policies or on the host application's access control, and it is unclear which applies here. Confirm with the maintainer whether policies ship with the package or whether you must implement gating yourself before exposing freelancer or payout data.
- Does Tomato Freelancers have a test suite or CI pipeline?
- There is no visible test coverage or CI signal for the 0.0.1 release. Single-vendor, early-stage packages in a niche ecosystem have a high dormancy rate, so the absence of tests is a real maintenance consideration rather than a formality. Ask whether CI runs against the Laravel versions you care about before depending on the package.
- What are the alternatives to tomato-freelancers for managing freelancers in Laravel?
- The closest alternative is building the freelancer, engagement, and payout models yourself as a small domain module, which keeps authorization and schema ownership in your hands. Other options are a general-purpose CRM or project-management package, or a Filament-based admin starter that you extend. Tomato Freelancers makes sense mainly if you are already inside the TomatoPHP ecosystem and want the CRUD scaffolding for free.
Weaver
How can I help you explore Laravel packages today?