Tagged: atlas
Pages with this tag
Continuous Develop & Deploy
1The everyday loop for a live CodeCanyon Laravel app — code, test locally, ship through the selected non-production target then production behind a database safety gate, and sync server-side changes back into git.
1 · Ship — code → test → deploy
2The 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.
8 · Dev tooling
3Decide which local-development power-ups to adopt — Atlas schema management, a database GUI (Bytebase), Redis caching via Herd Pro, and a right-sized debug-tools stack. None block launch; each has a free fallback.
9 · Atlas Cloud
4Decide whether to register your schema with Atlas Cloud for versioned migration tracking — open the SSH tunnel, build a baseline migration from the selected non-production schema, push it to Atlas Cloud, apply the baseline to that target, and wire up GitHub CI. Requires an active Atlas Cloud license; free alternatives noted.
Implement Vendor Updates
5Apply 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
6Diff 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.
Database & migrations
7How 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.
Schema management
8Extending 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.
Deploy commands
9Ship, 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.