Skip to content

CLI and Operations

Jump to bottom
Precious Lyson edited this page Nov 11, 2026 · 1 revision

CLI and Operations

Operations

The Artisan executable is part of the generated application, not this framework library checkout. Run commands from the application root and use its own command list as the authoritative reference:

php artisan list
php artisan help run:dev

Common command families

The framework source includes commands in these areas (availability depends on app registration):

Purpose Examples
Development server run:dev, stop:dev
Database db:test-connection, db:migration:*, db:seeder:*, db:factory:*
Views view:make, view:make-layout, view:make-partial
Providers provider:list, provider:make, provider:info
Queues queue:init, queue:work, queue:status, queue:failed
Scheduler scheduler:list, scheduler:run, scheduler:status
Notifications notify:channels, notify:list, notify:test

Wildcard groups above are shorthand, not literal shell commands. Check php artisan list and command-specific help for required arguments and options.

Tests

The framework package declares this Composer script:

composer test

For the exact test setup and available commands, inspect the scripts and dev dependencies in your application's composer.json. Do not assume commands for coverage, linting, static analysis, or Docker exist unless the app configures them.

Production principles

  • Install only production dependencies and optimize Composer's autoloader:

    composer install --no-dev --optimize-autoloader

  • Provide secrets and environment-specific configuration through the deployment platform.

  • Disable debug mode and prevent public access to configuration, logs, and source files.

  • Run database migrations as a controlled release step with backups and a rollback plan.

  • Run workers under a process supervisor; monitor restarts, queue depth, and failed jobs.

  • Configure health checks, logs, backups, TLS, and resource limits.

  • Verify permissions: only required runtime directories should be writable by the web process.

  • Keep dependencies and the PHP runtime patched.

Do not run caching/optimization commands merely because another PHP framework documents them. Confirm that the installed app provides the command and that cached configuration is appropriate for the deployment.

Deploy checklist

  • Tests pass in the same runtime version used in production.
  • Required PHP extensions and database driver are installed.
  • Production environment variables and secrets are present.
  • Debug mode is off; errors do not expose stack traces to clients.
  • Migrations and background workers are planned and monitored.
  • The web server points to the app's intended public document root.
  • Logs and backups have access controls and retention policies.
  • HTTPS and secure cookie behavior are enabled.

More

Machinjiri Docs

Clone this wiki locally