Skip to content
prod 352bb92
Browse

Tagged: codecanyon

All Tags
codecanyon
154 pages
5 related

Pages with this tag

2 · Apply the update

109

Tag 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

110

Re-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

111

Terse 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

112

Pick 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

113

Terse 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.

Security package update

114

composer/npm audit fix loop — backup, isolated branch, rigorous artisan checks, merge or rollback.

Server sync capture

115

Reverse-git — capture admin uploads, installer output, and server-side files back into develop before the next deploy wipes them. Peeled from MWF3.

Zaj module deploy

116

Deploy or update a ZajModules package — autoload dump, config publish, provider check, instant disable rollback. Peeled from MWF2.

Laravel/CodeCanyon — Guides

117

Focused, read-once Learn guides for the theory behind the CodeCanyon Laravel workflows — deployment, security, database, version control, architecture, dev environment, monitoring, and SaaS planning.

Architecture & systems

118

The bird's-eye view of how a Zajaly-style CodeCanyon Laravel app fits together — the four pillars, the event-driven flow, and where each piece is executed.

Database & migrations

119

How Laravel decides which migrations run, why additive-only discipline keeps vendor updates safe, and how schema-diff tools verify the database actually matches your intent.

Deployment concepts

120

How zero-downtime Deployer releases, symlinks, shared paths, and CI/CD safety nets actually work — the mental model before you run a single deploy.