Metator For Laravel Laravel Package

Product Decisions This Supports

• Faster path to production for Laravel products: v9 automates initialization of new sites from the current local .env, preserving custom settings, comments and multiline values. This reduces manual deployment setup and shortens time-to-first-deploy for new customer environments or internal apps.
• Standardized production configuration: Capability-based production defaults, separate production application keys, and site-owned database/Redis connections help enforce consistent, safer production environments without a bespoke runbook.
• Build vs. buy for deployment/provisioning tooling: If the team is evaluating whether to build internal Laravel provisioning scripts or adopt existing tooling, this package is a credible candidate for the narrow job of environment initialization, .env promotion, and repeatable provisioning.
• Roadmap input for platform/ops features: The release highlights where investment is going — idempotent provisioning, credential preservation on reruns, and conflict cleanup for local URLs/sockets/Redis credentials. PMs can use this to decide whether operational polish is a higher priority than new product features.
• Risk reduction in configuration drift: Preserving remote application values and credentials on ordinary provisioning reruns reduces accidental overwrites and environment-specific breakage, which supports reliability and compliance goals.

When to Consider This Package

• Consider it when: You are running Laravel/PHP applications that need repeatable production provisioning; you want to promote a local .env into production while preserving comments and custom values; you need production-specific defaults, separate application keys, and per-site database/Redis configuration; and your team values automated shell/PHP tests and CI coverage.
• Consider it carefully when: Your deployment process depends on scripts/.env.example as provisioning input — v9 changes provisioning to require the application’s local .env. This is a breaking operational change requiring upgrade planning, backup of customized scaffolding, and deliberate merging of recipe customizations.
• Look elsewhere when: You need a fully verified end-to-end provisioning-to-Deployer/Artisan/PHP-FPM integration — the release notes state disposable Ubuntu integration remains unverified. Also look elsewhere if you already have mature infrastructure-as-code (Terraform, Ansible, etc.), need broad non-Laravel support, or cannot accept a manual upgrade path with php artisan metator:install --force.

How to Pitch It (Stakeholders)

For executives: This release makes production setup for Laravel sites more repeatable and less error-prone. It preserves existing .env customizations, generates production-safe credentials and defaults, and avoids overwriting remote values on reruns. That means faster environment creation, fewer deployment surprises, and lower operational overhead — with the caveat that upgrading requires a deliberate backup-and-merge step.

For engineering: v9 improves production initialization by using the local .env as the source of truth, preserving comments and multiline values, applying capability-based defaults, generating a separate production key, and configuring site-owned database/Redis connections. It also clears conflicting local database URLs, MariaDB sockets and Redis credentials, including whitespace/export syntax and duplicate assignments. Reruns preserve existing remote values. Note the breaking change: provisioning now requires the local .env, and scripts/.env.example is no longer its input. Upgrade by backing up customized scaffolding before php artisan metator:install --force and merging recipe customizations deliberately. Tests passed (28 shell, 4 PHP, ShellCheck, PHP syntax, Composer validation, CI on PHP 8.4/8.5), but end-to-end Ubuntu provisioning integration remains unverified.