codegenie-be/laravel-config-cache-guard

Prevent Laravel from running with stale cached configuration after .env or config file changes. Built for shared hosting, FTP deployments and simple production apps.

v1.0.2 2026-06-17 17:04 UTC

Requires

• php: ^8.2
• illuminate/console: ^12.0|^13.0
• illuminate/support: ^12.0|^13.0

Requires (Dev)

• laravel/pint: ^1.0
• orchestra/testbench: ^10.0|^11.0
• pestphp/pest: ^3.0|^4.0

MIT

• Codegenie

• php
• laravel
• deployment
• artisan
• env
• ftp-deployment
• laravel-config
• shared-hosting
• config-cache
• codegenie
• laravel-config-cache
• config-cache-guard
• stale-config

README

by Codegenie

Prevent Laravel from running with stale cached configuration after .env or config/*.php changes.

Built for Laravel 12 and 13 apps on shared hosting, FTP deployments and simple production setups where php artisan config:cache can accidentally be forgotten.

This package is a safety net. The best production flow is still to run php artisan config:cache during deployment.

Quick start

composer require codegenie-be/laravel-config-cache-guard
php artisan config-cache-guard:install
php artisan config-cache-guard:status

The installer adds the guard to public/index.php before Laravel bootstraps.

Why this exists

Laravel can cache all configuration into:

bootstrap/cache/config.php

That is good for production performance, but it also means changes in .env or config/*.php are not reflected until the config cache is rebuilt.

This is easy to forget on shared hosting, FTP deployments or hosting panels where deploy hooks are limited. This package checks whether source configuration metadata changed before Laravel bootstraps. If it changed, it tries to rebuild Laravel's cached config before the request continues.

It does not replace a correct deployment pipeline. It protects you when the cache refresh step was skipped, forgotten or unavailable.

What it does

On normal requests, the guard performs a small metadata check against:

• .env
• .env.{APP_ENV} when APP_ENV is provided as a real server environment variable
• config/**/*.php

It only checks file metadata such as timestamps, file size and inode metadata. It does not read or store secret values.

When the signature changed, the guard takes a file lock and runs:

php artisan config:cache

The request then continues with the refreshed cached config.

What it does not do

• It does not read, log or store .env values.
• It does not use Redis, queues, workers, cron or a database.
• It does not add middleware to the request lifecycle.
• It does not rebuild config cache on every request.
• It does not replace a proper deployment process.

The package registers a small service provider, but only to expose Artisan commands. The runtime guard itself is loaded directly from public/index.php before Laravel bootstraps.

When to use this package

Use it when:

• you deploy Laravel through FTP or shared hosting
• your deploy process sometimes forgets php artisan config:cache
• your hosting panel has limited deployment hooks
• you want a small safety net against stale config cache
• you want to avoid queues, Redis, cron or background workers

Do not use it as a replacement for a correct deployment pipeline.

How it works

HTTP request
  -> public/index.php
  -> bootstrap guard runs before vendor/autoload.php
  -> build metadata signature from .env and config/**/*.php
  -> compare signature with bootstrap/cache/config-source.signature
  -> unchanged: continue immediately
  -> changed: lock, run php artisan config:cache, continue
  -> failed rebuild: remove stale config cache, then continue without cached config

This order is important. A Laravel middleware or service provider is too late for this job, because Laravel may already have loaded the old cached config by then.

Installation

composer require codegenie-be/laravel-config-cache-guard
php artisan config-cache-guard:install

The installer adds this line to public/index.php:

require __DIR__ . '/../vendor/codegenie-be/laravel-config-cache-guard/bootstrap/guard.php';

It must be placed before:

require __DIR__ . '/../vendor/autoload.php';

A typical public/index.php should look like this:

<?php

use Illuminate\Foundation\Application;
use Illuminate\Http\Request;

define('LARAVEL_START', microtime(true));

require __DIR__ . '/../vendor/codegenie-be/laravel-config-cache-guard/bootstrap/guard.php';

require __DIR__ . '/../vendor/autoload.php';

/** @var Application $app */
$app = require_once __DIR__ . '/../bootstrap/app.php';

$app->handleRequest(Request::capture());

Status check

php artisan config-cache-guard:status

This checks:

• whether the guard is enabled
• which failure cooldown is configured
• whether the guard is installed in public/index.php
• whether bootstrap/cache is writable
• whether cached config exists
• whether the signature file exists
• whether a failed-rebuild marker exists
• whether exec() is available
• which PHP CLI binary will be used

The command also prints a short result line such as ready, not installed, disabled or automatic rebuild unavailable.

Requirements

• PHP 8.2 or higher
• Laravel 12 or 13
• A writable bootstrap/cache directory
• exec() and a working PHP CLI binary for automatic cache rebuilding from web requests

Compatibility

Laravel	Package target	PHP range	Framework status
12	Supported	8.2 - 8.5	Security fixes until February 24, 2027
13	Supported	8.3 - 8.5	Security fixes until March 17, 2028

PHP 8.2 is security fixes only until December 31, 2026. For new production projects, prefer PHP 8.4 or PHP 8.5 when your hosting supports it.

Useful references:

• PHP supported versions: https://www.php.net/supported-versions.php
• Laravel release support policy: https://laravel.com/docs/13.x/releases

Environment options

These values must be real server environment variables. They are not read from Laravel config because the guard runs before Laravel bootstraps.

Variable	Default	Description
CONFIG_CACHE_GUARD_ENABLED	true	Set to false, 0, off or no to disable the guard.
CONFIG_CACHE_GUARD_FAILURE_COOLDOWN	60	Number of seconds to wait after a failed rebuild before trying again.
CONFIG_CACHE_GUARD_PHP_BINARY	auto-detect	Optional full path to the PHP CLI binary.
PHP_CLI_BINARY	auto-detect	Secondary PHP CLI binary override.
APP_ENV	optional	When provided externally, .env.{APP_ENV} is included in the metadata signature.

Example:

CONFIG_CACHE_GUARD_ENABLED=true
CONFIG_CACHE_GUARD_FAILURE_COOLDOWN=60
CONFIG_CACHE_GUARD_PHP_BINARY=/usr/bin/php

Files written by the guard

The guard may create or update these files inside bootstrap/cache:

File	Purpose
config.php	Laravel's cached configuration, created by php artisan config:cache.
config-source.signature	Metadata signature of .env and config/**/*.php.
config-cache-refresh.lock	File lock to avoid concurrent cache rebuilds.
config-cache-refresh.failed	Short cooldown marker after a failed rebuild attempt.

Failure behavior

Situation	Behavior
No config change	Continue immediately.
Config changed and rebuild succeeds	Continue with refreshed cached config.
Config changed and exec() is disabled	Remove stale cached config and continue without cached config.
Config changed and PHP CLI is not found	Remove stale cached config and continue without cached config.
Rebuild fails	Remove stale cached config and wait for the failure cooldown before retrying.

Removing stale config is intentional. Running uncached config is slower, but safer than continuing with old configuration.

Testing manually

After installation, you can test the guard like this:

php artisan config:cache
php artisan config-cache-guard:status

Then change a value in a file such as config/app.php or update its modified time:

touch config/app.php

Load the application once in the browser. If exec() and PHP CLI are available, the guard should rebuild bootstrap/cache/config.php and update bootstrap/cache/config-source.signature.

Recommended production flow

Use this package as a fallback, not as your primary deployment strategy.

A solid deployment should still include:

php artisan config:cache

This package protects you when that step is forgotten, skipped or not available on shared hosting.

Known limitations

• Automatic rebuilding from a web request requires exec() and a working PHP CLI binary.
• Change detection is metadata-based for performance. It uses file timestamps, size and inode metadata instead of reading .env values.
• This package is a fallback safety net. It should not replace a correct deployment pipeline that runs php artisan config:cache.

Troubleshooting

The status command says exec available: no

Your hosting disables exec(). The guard can still remove stale cached config, but it cannot rebuild a new cached config automatically from a web request.

Recommended fix:

php artisan config:cache

Run this during deployment or from your hosting control panel if available.

The wrong PHP binary is detected

Set the binary manually:

CONFIG_CACHE_GUARD_PHP_BINARY=/usr/bin/php

Then run:

php artisan config-cache-guard:status

The installer cannot update public/index.php

Add the require line manually before vendor/autoload.php:

require __DIR__ . '/../vendor/codegenie-be/laravel-config-cache-guard/bootstrap/guard.php';

I want to disable the guard temporarily

Use a real server environment variable:

CONFIG_CACHE_GUARD_ENABLED=false

Uninstall

Remove the require line from public/index.php:

require __DIR__ . '/../vendor/codegenie-be/laravel-config-cache-guard/bootstrap/guard.php';

Then remove the package:

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

Optional cleanup:

rm -f bootstrap/cache/config-source.signature
rm -f bootstrap/cache/config-cache-refresh.lock
rm -f bootstrap/cache/config-cache-refresh.failed

Security and privacy

This package is intentionally small and file-based.

• It does not read .env values.
• It does not store secrets.
• It does not send data to external services.
• It does not use a database.
• It does not require Redis, queues, workers or cron.
• It uses a file lock to avoid concurrent rebuilds.
• The rebuild command is fixed to php artisan config:cache; paths are escaped and no user input is passed to the shell.

Please report security issues privately. See SECURITY.md.

License

The MIT License. See LICENSE.md.

About Codegenie

Codegenie builds Laravel websites and web applications with a focus on simplicity, reliability and production-friendly deployment.

https://www.codegenie.be