Skip to content
ZajLibrary
prod 352bb92
Browse

Tagged: migrations

All Tags
migrations
17 pages
5 related

Pages with this tag

ZajModules vs customizations

13

The core mental model — deciding whether a change is a new ZajModule, a vendor customization, or a schema extension, and why that split keeps your app update-safe.

Path: /tech-stack/laravel/codecanyon/learn/handbooks/01-zajmodules-vs-customizations/

Schema management

14

Extending a vendor's database safely — additive _zaj migrations that add marked columns to vendor tables, zajm_ module tables, soft references, and never editing a vendor migration.

Path: /tech-stack/laravel/codecanyon/learn/handbooks/03-schema-management/

Deploy commands

15

Ship, 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.

Path: /tech-stack/laravel/codecanyon/resources/cheatsheets/operations/01-deploy-commands/

Customization decision

16

The one-screen routing for any change to a CodeCanyon Laravel app — vendor file edit → vendor-customizations overlay, new functionality → ZajModule, vendor-table column → additive _zaj migration — so nothing is lost on the next vendor update.

Path: /tech-stack/laravel/codecanyon/resources/cheatsheets/operations/02-customization-decision/

Gotchas

17

The CodeCanyon Laravel traps that bite — per-environment APP_KEY, APP_DEBUG off the box, the utf8mb4 schema, the vendor overlay that composer install reverts, secrets in server sync, and Cloudflare Full (Strict) SSL — each with the one-line fix.

Path: /tech-stack/laravel/codecanyon/resources/cheatsheets/operations/03-gotchas/