deployment-workflow_skill

This skill helps you understand and troubleshoot Laravel deployment workflows, health checks, rollbacks, and cache management to reduce outages.

TypeScript

1

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill hackur/web-standards-playground-showcase --skill deployment-workflow

SKILL.md10.5 KB

Overview

This skill documents a human-only deployment workflow for staging and production using Laravel Deployer. It explains safe deployment steps, health checks, cache and package handling, and rollback procedures for troubleshooting and planning. It is for understanding and operational guidance only — deployments must be executed by humans.

How this skill works

The workflow describes a parameterized, DRY set of shell and Deployer tasks that run a 12-step deployment sequence: update code, link shared files, clear composer cache, install vendors with --prefer-source, cache Laravel artifacts, run migrations, build assets, and symlink the release. It includes automated health checks with retry logic, package verification to catch missing files early, and a rollback mechanism that swaps the current symlink to the previous release. Scripts and helper libraries centralize configuration and deployment functions for both staging and production.

When to use it

Review deployment architecture and sequence before a release
Troubleshoot failed deployments and analyze verbose logs
Run pre-deployment validations and package verification
Plan rollback and recovery procedures
Document deployment steps and hand off to operators

Best practices

Treat all deploy commands as HUMAN-ONLY; never automate destructive server commands via LLMs
Keep environment config in a single lib to avoid drift and duplication
Always clear Composer cache and use --prefer-source for VCS packages to avoid corrupted artifacts
Include package verification to fail fast with clear diagnostics
Run health checks after deploy and roll back automatically or manually on failure

Example use cases

Walk through a failed production deploy to identify missing package files and clear composer cache
Validate staging deploy with fresh database seeding and health endpoint checks
Perform a safe manual rollback by switching current symlink to the previous release
Use verbose deploy logs to confirm Composer cache clearing and vendor installation method
Apply the deployment checklist before an emergency production fix

FAQ

No. All scripts and commands are documented for human execution only. The guidance is for understanding, troubleshooting, and safe manual operation.

What triggers a rollback?

A failing health check or clear runtime errors after deploy should trigger a rollback. The workflow preserves releases and swaps the current symlink to the previous release to recover quickly.