Tagged: vendor updates
Pages with this tag
CodeCanyon workflows
1Command 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.
Implement Vendor Updates
2Apply 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
3Diff 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
4Tag 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.
Schema management
5Extending 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.
Version management
6Two version lines that never get confused — SemVer for your own fork versus the vendor's author-vX.X.X snapshots — plus CHANGELOG discipline that keeps upgrades calm.