Laravel/CodeCanyon
This is the home base for deploying, customizing, and maintaining a CodeCanyon Laravel application (a WorkDo/Dash-style SaaS bought from CodeCanyon). The work splits into five workflows — start with the one that matches what you need to do right now.
Which workflow am I in?
Section titled “Which workflow am I in?”flowchart TD Q{What do you need<br/>to do right now?} Q -->|First time:<br/>ZIP to live site| W1[1 · Set up a New App] Q -->|Ship code changes<br/>safely| W2[2 · Continuous Deploy] Q -->|Add custom features<br/>without breaking updates| W3[3 · Implement Customizations] Q -->|The vendor released<br/>a new version| W4[4 · Vendor Updates] Q -->|Production is broken<br/>right now| W5[5 · Emergency Hotfix]The workflows
Section titled “The workflows” 1 · Set up a New App ZIP to production, AI-assisted end to end. 12 phases: AI system, repo, local dev, deploy pipeline, staging, superadmin, hardening, configure, growth, QA, launch, production.
2 · Continuous Deploy The everyday loop: code, test, ship safely, and capture server changes back into git.
3 · Implement Customizations Add features without losing them on the next vendor update — the ZajModules + vendor-customizations system.
4 · Vendor Updates Apply a new vendor release: compare schemas, apply the update, and restore your customizations.
5 · Emergency Hotfix Production is down: the fast, safe path to patch and roll back.
After setup — operations router
Section titled “After setup — operations router”Setup got the app live once. Operations workflows is the post-setup command center: one decision tree for WF-SHIP, WF-SYNC, vendor updates, hotfix, rollback, security patches, modules, and docs — each linking into the playbooks and runbooks above.
Supporting material
Section titled “Supporting material” Concepts handbook The mental models: ZajModules vs vendor customizations, the three-tier admin model, schema and version management.
Cheat sheets Glanceable command and decision references.
Templates Deployer, .env, .htaccess, and .gitignore starters.
Kits Reusable bundles like the vendor-customization restore script.
Vendors & tools
Section titled “Vendors & tools”The directory entries this collection leans on:
Vendors WorkDo — the CodeCanyon vendor family these playbooks target (Dash SaaS and friends) — and CodeCanyon, the Envato marketplace the app is bought from.
Tools Atlas — schema-diff + migration tracking behind the deploy and vendor-update safety gates — and Deployer, the zero-downtime PHP deployment used by the pipeline.