Tagged: laravel
Pages with this tag
4 · Run the installer
37Raise the PHP-FPM and nginx timeouts so big migration runs don't 504, pre-flight four preconditions, complete the installer, then capture every seeded/default credential safely.
5 · Verify migrations & schema
38Confirm every migration ran (modules included), troubleshoot pending ones the right way, capture a normalized schema baseline for cross-environment diffs, then run the 11-point gate that proves the app actually works.
6 · Commit & secure
39Commit 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.
7 · Shared-hosting readiness
40Verify that the hosting account has the Admin-Server toolkit before the deploy pipeline starts, or run the shared-hosting playbook first.
8 · Dev tooling
41Decide which local-development power-ups to adopt — Atlas schema management, a database GUI (Bytebase), Redis caching via Herd Pro, and a right-sized debug-tools stack. None block launch; each has a free fallback.
Phase 4 · Deploy pipeline
42Stand up everything that makes deployment possible — Deployer for zero-downtime releases, environment domains + SSL, production .env templates, and (recommended) CI, DNS email records, and a CDN — so Phase 5 can run the first observed non-production deploy.
1 · Deployer (zero-downtime)
43Install 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 · Production .env
44Assemble a safe production env source — bidirectional drift check against .env.example, a Git-history secret scan, production flags, and a secrets-manager render check. Server upload and runtime verification happen in Phase 5 or Phase 12.
Phase 5 · Staging deploy
45Take the app from "runs locally" to "runs on a real non-production server" — provision the selected target, point DNS, ship the first atomic release, run the web installer, verify the schema, prove rollback, and open any standing observation follow-up.
1 · Pre-flight & provision host
46Consume the Phase 4 handoff, pin Composer to the confirmed deploy PHP, run the canonical pre-flight, prepare and push the selected non-production branch, then scaffold the server — deploy tree, .user.ini limits, and the shared .env with APP_KEY left empty.
2 · DNS + SSL
47Confirm the non-production domain resolves to the server and serves a valid TLS chain before the first release lands — a deploy onto an unresolved or untrusted host wastes a round-trip.
3 · First release
48Run 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.