Skip to the main content
{}

Open-source Laravel tool

Laravel Config Cache Guard

Composer package that prevents Laravel from using stale configuration or route cache after an FTP or shared-hosting deployment.

View on GitHub(Opens in a new window)Discuss a safe Laravel deployment

When should you use this tool?

Use this package as a safety net when deploying through FTP, cPanel, Plesk or shared hosting and a skipped cache rebuild must never serve old configuration or routes.

Changed deployment sources are detected before Laravel boots, stale cache is safely bypassed and repair can complete after the response even without exec.

Who is this tool for? Laravel teams that use config or route cache but do not always have SSH, exec or reliable deployment hooks.

Quickstart

Local installation

Use the repository as a starting point. Always verify your own project requirements and lockfiles before production use.

composer require codegenie-be/laravel-config-cache-guard

Key capabilities

  • 01Detects relevant changes before Laravel can load stale config or route cache
  • 02Supports Laravel 12 and 13 on PHP 8.2 through PHP 8.5
  • 03Works with FTP, cPanel, Plesk and shared-hosting deployments
  • 04Repairs through PHP CLI or an internal Artisan call when exec is unavailable
  • 05Requires no Redis, queue, worker, cron, database or public repair endpoint
  • 06Does not read, log or store values from .env

Checking a deployment

The guard is a safety net for hosting with limited deployment capabilities. A normal deployment with explicit cache commands remains preferable when reliably available. Install the package in a test copy and inspect the status without sharing an .env file.

bash
php artisan config-cache-guard:status

Compatibility and limits

  • Laravel 12 requires PHP 8.2 or later; Laravel 13 requires PHP 8.3 or later. Also check the chosen package version’s Composer requirements.
  • The documented flow protects against known-stale cache before Laravel boots and uses Laravel Artisan for repair after the response. It needs no permanent worker.
  • Keep env() in configuration files and use config() in application code. A guard does not repair incorrect env() usage.
  • Verify both changed configuration and routes in the test environment. A status report does not replace a functional check.
Read about configuration and route cache

Another useful Laravel resource

Laravel Livewire Multi-step Form

Open source

Open-source Composer package for Laravel 12/13 and Livewire 3.6+/4: a configurable multi-step form with validation, a review step and a controlled submission hook.

Laravel teams integrating multi-step forms without handing application persistence to a package.

View the toolGitHub(Opens in a new window)

Adapt a tool to your own Laravel project?

Codegenie can tailor the flow, styling, validation or deployment to your existing application.

Discuss your project