laravel-deploy

Standardize Laravel 12 deployment procedures with atomic symlink swaps and health checks.

Updated Apr 15, 2026
One-click install
npx skills add https://github.com/gab3mioni/laravel-claudecode-toolkit --skill laravel-deploy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: laravel-deploy
Source: https://github.com/gab3mioni/laravel-claudecode-toolkit/tree/main/skills/laravel-deploy
Command: npx skills add https://github.com/gab3mioni/laravel-claudecode-toolkit --skill laravel-deploy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill eliminates the stress and downtime associated with shipping Laravel 12 applications by providing a standardized, verifiable checklist for runtime environments, CI pipelines, and infrastructure management.

Core Features & Use Cases

  • Zero-Downtime Deployments: Orchestrates atomic symlink swaps, worker recycling, and health checks to ensure traffic is never served by broken or stale code.
  • Infrastructure Guardrails: Provides battle-tested patterns for Docker multi-stage builds, supervisord/systemd worker management, and scheduler cluster safety.
  • Use Case: Use this skill when configuring a new CI/CD pipeline or troubleshooting production issues like 502 errors during releases, stale code execution, or session invalidation.

Quick Start

Use the laravel-deploy skill to audit the current deployment pipeline and verify zero-downtime readiness.

Frequently Asked Questions about laravel-deploy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I achieve zero-downtime deployment for a Laravel application?

Zero-downtime deployment for Laravel is achieved by orchestrating atomic symlink swaps, recycling workers, and running health checks so traffic is never served by stale or broken code.

What causes 502 errors during Laravel releases and how can I prevent them?

502 errors during Laravel releases are caused by traffic hitting broken or stale code, which you prevent by implementing atomic symlink swaps and health check verification in your CI/CD pipeline.

How do I manage Laravel queue workers and schedulers in Docker without stale code execution?

You manage Laravel queue workers and schedulers in Docker by using supervisord or systemd for worker recycling and applying scheduler cluster safety patterns to prevent stale code execution.

What is the best way to configure environment-agnostic secret management for Laravel CI/CD pipelines?

Configuring environment-agnostic secret management for Laravel CI/CD pipelines involves standardizing runtime configurations to securely inject secrets without hardcoding them into your Docker containers or repository.

Do I need Docker multi-stage builds to deploy Laravel 12 with zero downtime?

Docker multi-stage builds are used to create optimized infrastructure guardrails for Laravel 12 deployments, ensuring reliable runtime environments and standardized containerization for zero-downtime releases.

Why does my Laravel deployment result in session invalidation after an atomic symlink swap?

Session invalidation after an atomic symlink swap occurs when runtime configurations are mismanaged, which you resolve by standardizing environment-agnostic setups and verifying health checks before traffic routing.