Tagged: codecanyon
Pages with this tag
1 · Ship — code → test → deploy
13The 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.
2 · Server sync — capture server changes
14Capture untracked server / admin-panel changes (uploads, installer output, config) back into git with WF-SYNC before a deploy overwrites them — reviewing the file list first and never staging secrets.
Implement Customizations
15Add custom features to a CodeCanyon Laravel app without losing them on the next vendor update — the ZajModules + vendor-customizations system.
1 · The decision rule
16Three questions that route any change to the right update-safe home — a ZajModule package, the vendor-customizations overlay, or a _zaj migration that adds marked columns to a vendor table — so nothing you build is lost on the next vendor update.
2 · Build a ZajModule
17Build new functionality as a self-contained ZajModule package under packages/ZajModules/ — directory structure, namespace and naming conventions, and the event-driven pattern that keeps it isolated from vendor code and safe across updates.
3 · Vendor customizations
18When a vendor file must be edited, store the edited copy in the resources/vendor-customizations/ overlay that mirrors vendor paths, mark your changes with ZAJ:BEGIN/END markers, and re-apply the overlay after every composer install overwrites vendor/.
4 · Track and restore
19Keep a MOD-NNN tracking log and a _CUSTOMIZATIONS file documenting every vendor patch, and run restore-vendor-customizations.php to re-apply your overlay automatically after composer install or a vendor update overwrites vendor/.
Emergency Hotfix
20Production is broken — the fast, safe path to patch a live CodeCanyon Laravel app and roll back if needed.
1 · Hotfix forward
21Branch 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
22Restore 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.
CodeCanyon workflows
23Command router for a CodeCanyon Laravel app across its whole lifecycle — from first-time setup through daily operations like ship, vendor updates, hotfix, rollback, server sync, security, modules, and docs.
Set up a New CodeCanyon App
24Deploy a CodeCanyon Laravel application from ZIP to production, step by step — AI-assisted, 12 phases.