Tagged: deployer
Pages with this tag
1 · Hotfix forward
1Branch from production state, make the minimal scoped fix, fast-track straight to production skipping staging, then back-merge so the fix survives the next release.
2 · Roll back
2Restore the last good release via the deployer symlink or a known-good tag — when to roll back versus fix forward, the database-migration caveat, and post-incident steps.
6 · Commit & secure
3Commit the repo-safe installer artifacts, document any author patches in the shipped vendor tree, verify deploy symlinks and shared_files, then lock down /install and /update with layered defense.
1 · Deployer (zero-downtime)
4Install Deployer and author deploy.php for atomic releases — symlinked current → timestamped releases, shared storage and .env, retention, hooks, server binary paths, and an SSH-verified dry run.
3 · First release
5Run the atomic first deploy, confirm APP_KEY and clear caches with the versioned PHP binary, verify the Deployer directory tree and the .env symlink (a 5-second check that prevents a 90-minute outage), confirm demo content, then loosen permissions for the installer.
Deployment concepts
6How zero-downtime Deployer releases, symlinks, shared paths, and CI/CD safety nets actually work — the mental model before you run a single deploy.
Laravel/CodeCanyon — Templates
7Copy-and-fill starter files for CodeCanyon Laravel deployment — deployer, environment, web server, and git ignore.
Deployer — deploy.php
8The zero-downtime Deployer config for a CodeCanyon Laravel app — project block to fill in, smoke test, health check, and rollback baked in.