Tagged: laravel
Pages with this tag
1 · Pre-flight security hygiene (P0)
97Never skip this — rotate every test-mode key and non-production password that touched a chat or log, migrate plaintext credentials into a secrets manager, re-scope over-privileged service accounts, and record the audit.
2 · Release & first production deploy (P1–P2)
98Cut the changelog and version before deploying, then promote the verified non-production branch to the release branch, stage the production .env, deploy dry-run then real, run the installer (first deploy only), and verify it's live.
3 · Harden, verify & sync (P3–P7)
99Lock down installer-friendly permissions, verify schema parity against staging, review ServerSync, prove production mail flow, then sync all branches back to a shared base and tag the release as your rollback and audit anchor.
4 · Post-deploy monitoring & day-2 (P9)
100Watch closely through the first 24–48h — smoke tests, integration checks, performance/security spot-checks, log triage, and baselines — with rollback always one command away, then the abbreviated subsequent-deploy cycle.
Full roadmap & checklist
101The entire setup-new playbook on one page — 12 phases, every step, every gate. Read the workflow top to bottom or tick progress as you go.
Implement Vendor Updates
102Apply a new CodeCanyon vendor release without losing your customizations or breaking the database — compare the schema, apply the update on a branch, then restore your overlay.
1 · Compare the schema
103Diff the new vendor release against your frozen author-vX.X.X snapshot — list pending migrations, preview the SQL, run an Atlas schema diff, and classify every change by risk so a destructive operation never reaches the database by surprise.
2 · Apply the update
104Tag a backup, branch the frozen author baseline to author/vY.Y.Y, drop in the new vendor files, then merge to develop and run migrations safely — every step reversible until the update is proven.
3 · Restore customizations
105Re-apply your vendor-customizations overlay with the restore script after the clean vendor/ rebuild, re-scan for backdoor signatures, confirm every ZajModule, zajm_ table, and _zaj column survived untouched, verify the patches behaviourally, then deploy staging-first.
Laravel/CodeCanyon — Runbooks
106Terse one-operation command cards for Laravel/CodeCanyon — exact commands and checks, no teaching. Peeled from Mini-Workflows and playbook phases for when you already know the drill.
Authoring docs checklist
107Pick the doc type (playbook Part, module devdocs, concept guide, micro-workflow) and run the right template checklist before publishing. Peeled from MWF4 — meta for authors and agents.
Code → test → ship
108Terse 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.