Weave Code
Tomato Artisan Module Laravel Package
tomatophp/tomato-artisan-module
A Tomato PHP module that brings Laravel Artisan into your admin panel, letting you browse and run commands from a web interface instead of the terminal. Integrates with Tomato's modular ecosystem for quick setup and management.
artisan terminal to run artisan commands using GUI
Frequently asked questions about Tomato Artisan Module
- What is tomatophp/tomato-artisan-module and what does it do?
- tomatophp/tomato-artisan-module is a Tomato PHP module published on Composer that adds an Artisan terminal to a Laravel admin panel, letting you browse and run Artisan commands through a web interface instead of the CLI. It is built to integrate with Tomato's modular ecosystem, so setup follows the same pattern as other Tomato modules. The v1.0.0 release ships only a changelog link, so verify exact capabilities against the source before adopting.
- How do I install and configure tomato-artisan-module in a Laravel application?
- Install it with Composer using a pinned constraint, for example composer require tomatophp/tomato-artisan-module:1.0.0, in a Laravel app that already follows TomatoPHP conventions. Laravel package discovery should register the service provider, but confirm whether you need to publish configuration, run migrations, or register the module in your Tomato admin panel. Start in a sandbox app and review the routes and middleware before enabling it anywhere else, and check that its dependency constraints do not collide with your existing packages.
- Which Laravel and PHP versions does tomato-artisan-module support?
- The v1.0.0 release notes do not include a compatibility matrix, so supported Laravel and PHP versions must be confirmed from the composer.json constraints and the source. Check those constraints against your host application before installing, since the release provides no documented upgrade or support guarantees. Pinning the version and recording the changelog link is the safest baseline until clearer compatibility information is published.
- Does tomato-artisan-module run arbitrary Artisan commands or only allowlisted ones?
- That behavior is not documented in the release, and it is the single most important thing to verify in the source before adoption. If the module executes arbitrary Artisan commands as the web user, the security surface is much larger than a curated allowlist of registered commands. Review the command resolution and dispatch code directly and only deploy behind authorization controls you own.
- Is it safe to expose Artisan command execution in a production admin panel?
- Treat any admin-facing Artisan runner as high risk until you have confirmed authorization, command allowlisting, audit logging, timeouts, and environment restrictions. Artisan can run destructive operations, so web-triggered execution should be limited to trusted roles, guarded outside non-production environments, and fully logged with the acting user. Do not expose command execution to production users until those controls are verified in the code.
- Do I need a TomatoPHP admin panel to use this module?
- The package is described as a Tomato PHP module that integrates with Tomato's modular ecosystem, which strongly suggests it assumes a TomatoPHP-style admin panel. If you run a plain Laravel install with a different admin stack, integration may require extra work or may not be a good fit. Native Artisan, the scheduler, and queue workers cover most command-running needs without an extra module.
- Does tomato-artisan-module add migrations, config files, routes, or middleware I need to review?
- v1.0.0 has no detailed release notes, so inspect the repository for config files, migrations, published assets, and route or middleware registrations rather than assuming. Review anything it registers against your existing deployment scripts, scheduler jobs, and operational runbooks. Confirm whether its routes are guarded by the panel's auth middleware or require additional protection.
- Are long-running Artisan commands queued, or do they run synchronously in the browser?
- Long-running Artisan commands should generally be queued rather than executed synchronously inside an HTTP request, which can hit PHP execution limits and tie up web workers. The release materials do not state how the module handles long-running commands, so inspect the source for timeouts, output buffering, concurrency limits, and queuing behavior. Size your queue workers accordingly if you route heavy commands through the UI.
- How should I test and roll out tomato-artisan-module before production?
- Install it in a representative non-production app with the version pinned, verify package discovery and any publishes or migrations, and review routes, middleware, and command resolution. Run smoke tests for successful execution, permission denial, and failure handling, then roll out behind a feature flag while monitoring usage and errors. Assign an owner for version pinning, dependency updates, and changelog review given the sparse release notes.
- What is the maintenance status and upgrade policy for tomato-artisan-module v1.0.0?
- The only release evidence for v1.0.0 is a changelog link, with no enumerated fixes, breaking changes, or migration notes, so treat it as a baseline rather than an upgrade review. Support quality is unverified: check maintainer responsiveness, documentation depth, issue backlog, and whether the package is part of a broader supported TomatoPHP suite. Pin the version and document your own upgrade and review policy until the project publishes clearer compatibility and release information.
Weaver
How can I help you explore Laravel packages today?