SeviaFlow Get Started

DevTools: Commands

These are the public Artisan commands provided by seviaflow/devtools. Run them from the Laravel application root. php artisan help seviaflow:command-name also shows the options registered by your installed version.

Common flags and command-specific options

Flags are command-specific; use only the options listed for the command you are running. In particular, --dry-run is not supported by seviaflow:install.

OptionEffectUse it when
--dry-runFor resource-part generators, prints the target without writing. Discovery is report-only by default when --generate is absent; --dry-run does not override --generate, so omit --generate to guarantee no files are written.Review what a generator would create before changing the application.
--forceAllows an existing generated or published file to be overwritten where that command supports overwriting.Only when you have reviewed the existing file and intend to replace it.
--migrateRuns Laravel migrations after seviaflow:install publishes available package files.When you want the installer to apply the published migrations now.
--with-views, --with-stubsAlso publishes UI views or SeviaFlow stubs when those publish tags are available.When you need to customize a view or generated-code stub in the host application.
--dangerGenerates an action or bulk action with dangerous styling and confirmation enabled.When the generated operation has a consequential effect.

Install and diagnose

CommandWhat it doesOptions
seviaflow:installPublishes configuration, migrations, and UI assets for installed SeviaFlow packages. It can optionally publish views and stubs.--force, --migrate, --with-views, --with-stubs
seviaflow:listLists registered Resources and relevant SeviaFlow configuration.None.
seviaflow:statusReports enabled SeviaFlow modules and route status.None.
seviaflow:doctorRuns installation diagnostics and reports checks that need attention.None.
seviaflow:cacheWarms SeviaFlow metadata caches.None.
seviaflow:cache-clearClears SeviaFlow metadata and UI caches.None.

Discover Eloquent models

CommandWhat it doesOptions
seviaflow:discoverScans configured model folders and prints Resource suggestions. It writes files only when --generate is supplied.--dry-run, --generate, --force, --models=, --path=, --with-schema, --ignored=

Use --models=Customer,Order to inspect only named models, --path=app/Domain/Models to scan another folder, and --ignored=App\Models\AuditLog to exclude models from this run. --with-schema asks DevTools to inspect the database tables and suggest fields, filters, relations, and workflow candidates.

For example, first inspect the configured model path and database schema, then preview the files a Resource generator would create:

php artisan seviaflow:discover --with-schema
php artisan seviaflow:make-resource Customer --model=Customer --dry-run

The discovery command prints suggestions and writes no files because this command omits --generate. The generator's --dry-run prints target paths only. After reviewing them, run the generator without --dry-run to write the starter files:

php artisan seviaflow:make-resource Customer --model=Customer

Review the generated fields and register the Resource explicitly; see Resource Registration. Do not add --force unless you intend to replace existing generated files.

Generate Resource parts

CommandGeneratesArguments and options
seviaflow:make-resourceA Resource class and its extracted form/table structure.name, --model=, --force, --dry-run
seviaflow:make-formAn extracted form definition for a Resource.name, --resource=, --force, --dry-run
seviaflow:make-tableAn extracted table definition for a Resource.name, --resource=, --force, --dry-run
seviaflow:make-sectionAn extracted form section for a Resource.name, --resource=, --force, --dry-run
seviaflow:make-actionAn extracted one-record action class.name, --resource=, --danger, --force, --dry-run
seviaflow:make-bulk-actionAn extracted bulk action class.name, --resource=, --danger, --force, --dry-run
seviaflow:make-workflow-handlerA handler class for a Resource workflow transition.name, --resource=, --force, --dry-run

For an extracted-part generator, name is the class name to create and --resource identifies the Resource it belongs to. make-resource instead takes the Eloquent model class through --model. Generators create starting files; register the Resource and review generated fields, relationships, validation, and authorization in your application. See Discovery & Generation for a safe discovery workflow.