在Google App Engine标准环境部署Laravel 6应用遇缓存路径错误

I’ve been there too—deploying Laravel to GAE Standard can feel like navigating a maze of path permissions and environment quirks. Let’s break down how to fix your cache path error and the favicon 500 issue step by step:

1. Force Laravel to Use /tmp and Ensure Required Directories Exist #

The root problem here is that Laravel expects certain cache directories to exist, but GAE’s /tmp folder doesn’t come with the full framework/cache or framework/views structure pre-created. Update your bootstrap/app.php to set the storage path and manually create these directories on boot:

$app = new Illuminate\Foundation\Application(
    $_ENV['APP_BASE_PATH'] ?? dirname(__DIR__)
);

// Set storage path to GAE's writable /tmp directory
$app->useStoragePath(env('APP_STORAGE', '/tmp'));

// Create required cache directories if they don't exist
$storagePath = $app->storagePath();
$requiredDirs = [
    $storagePath . '/framework/cache/data',
    $storagePath . '/framework/views',
    $storagePath . '/logs',
];

foreach ($requiredDirs as $dir) {
    if (!file_exists($dir)) {
        mkdir($dir, 0755, true); // Recursively create directories
    }
}

This ensures that when Laravel tries to write cache files, the directories are already there with proper permissions.

2. Simplify Your app.yaml Environment Variables #

You don’t need to define every single cache file path individually—let Laravel handle the defaults once the base storage path is set. Trim your env_variables to:

env_variables:
    APP_ENV: production
    APP_KEY: your-actual-app-key-here
    CACHE_DRIVER: file
    SESSION_DRIVER: cookie
    APP_STORAGE: /tmp
    VIEW_COMPILED_PATH: /tmp/framework/views

The VIEW_COMPILED_PATH is the only one you need to explicitly set because Laravel’s default compiled view path might not map correctly to /tmp otherwise.

3. Fix Your Composer Scripts (Stop Clearing Cache on Deploy) #

Running cache:clear or config:clear in your post-install-cmd is counterproductive on GAE. Instead, pre-compile your cache locally before deploying so GAE can use the ready-made files. Update your composer.json scripts:

"scripts": {
    "post-autoload-dump": [
        "Illuminate\\Foundation\\ComposerScripts::postAutoloadDump"
    ],
    "pre-deploy": [
        "php artisan config:cache",
        "php artisan route:cache",
        "php artisan view:cache"
    ]
}

Before deploying, run composer run pre-deploy locally. This generates cached config/routes/views that will work seamlessly on GAE—no need to recreate them in the restricted environment.

4. Fix the Favicon 500 Error #

GAE’s default handler forwards all requests to Laravel, including static files like favicon.ico. Add a static file rule to your app.yaml to handle this directly:

handlers:
    # Handle favicon first
    - url: /favicon.ico
      static_files: public/favicon.ico
      upload: public/favicon.ico
      secure: always

    # Serve other static assets
    - url: /(css|js|images)/.*
      static_files: public/\1/\2
      upload: public/(css|js|images)/.*
      secure: always

    # Forward all other requests to Laravel
    - url: /.*
      script: auto
      secure: always

This tells GAE to serve favicon.ico as a static file instead of sending it to Laravel’s router, which was causing the 500 error.

Quick Recap of Critical Fixes #

• Always create required cache directories in /tmp on app boot—Laravel won’t do this for you on GAE.
• Pre-compile caches locally instead of clearing them during deployment.
• Explicitly define static file handlers in app.yaml to avoid routing issues.

内容的提问来源于stack exchange，提问作者Gustavo Aguiar