Tagged: staging
Pages with this tag
Staging first deploy
1First staging release — branch prep, installer, hardening, migration verification, and DevLog evidence.
Continuous Develop & Deploy
2The everyday loop for a live CodeCanyon Laravel app — code, test locally, ship through the selected non-production target then production behind a database safety gate, and sync server-side changes back into git.
1 · Ship — code → test → deploy
3The everyday deploy loop (WF-SHIP) — decide small vs big, work on develop, clear the pre-deploy database safety gate (Atlas lint — STOP on DS102/DS103), then run develop → selected non-production target → production and tag the release.
Phase 5 · Staging deploy
4Take 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
5Consume 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.
Code → test → ship
6Terse deploy loop — local verify, pick Pattern A/B/C, run dep deploy or staging→production, post-deploy checks. Peeled from MWF1; teaching lives in the Ship playbook step.
The three-tier admin model
7Where your ops files live — Admin-Local in the project repo, Admin-Domain as per-domain runtime state, and Admin-Server shared across the whole hosting account.
Deploy commands
8Ship, server-sync, and rollback command sequences at a glance — develop → staging → production behind the Atlas pre-deploy gate (STOP on DS102/DS103), plus the three rollback options.