lc:deploy-checklist

To check Laravel production readiness, you need to audit environment variables, security middleware, cache drivers, and debug configurations. A static analysis of your project configurations identifies common misconfigurations and provides actionable remediation steps before deployment.

Before deploying a Laravel app, verify security configurations like HTTPS enforcement, CORS settings, and environment variables. You should also scan for potential debug leaks and ensure insecure middleware settings are resolved to prevent vulnerabilities in production.

Auditing Laravel environment variables and cache drivers involves scanning your application directory against production best practices. This checks environment configurations, queue connections, and mail settings to ensure adherence to production standards and identify performance bottlenecks.

Yes, a Laravel production readiness checklist detects debug statements and TODO comments during its code quality checks. It flags these unresolved items alongside missing HTTPS enforcement and insecure CORS settings to ensure application stability before release.

Yes, you can generate a pass/fail report for Laravel production misconfigurations by running a static analysis checklist. This report identifies configuration gaps and security vulnerabilities, providing specific remediation steps to achieve production readiness.