CodeCanyon workflows

The command router for a CodeCanyon Laravel app across its whole lifecycle — start with first-time setup (vendor ZIP → first deploy), then route any operation once the app is live (all five branches exist, Deployer wired, answering on staging and production).

Pick your situation in the tree below, then open the linked playbook or runbook for step-by-step detail. The operations branch condenses the consolidated ops reference from the Residoro corpus (Ops-Workflows.md).

How to use this

Mode	What to do
Agent-driven	Install zaj-laravel-codecanyon in Phase 1, then run /zaj-laravel-codecanyon with an action (ship, update, hotfix, …). The skill routes to the same workflows below.
Manual	Use the decision tree, open the matching playbook page, and run the steps there.
Describe the problem	Tell your agent what is wrong (“production is down”, “vendor released v11”, “logo uploaded on server”) — it should map you to one row in the catalog.

Replace placeholders from your project constitution (CLAUDE.md / CLAUDE.local.md), not hardcoded domain names:

Placeholder	Example	Source
[PROJECT]	waraq	Project constitution
[DOMAIN]	waraq.ai	Local secrets file
[SSH_STAGING_ALIAS]	Hostinger-Zajaly	SSH config
[SSH_PRODUCTION_ALIAS]	Hostinger-Waraq	SSH config
[DEPLOY_PATH]	~/domains/[DOMAIN]/public_html	Hosting layout
[PHP_BIN]	php or /opt/alt/php83/usr/bin/php	Server-specific
[AUTHOR_VERSION]	v10.4	Frozen vendor branch
[YOUR_VERSION]	v1.0.0-b	git tag --list "v*" --sort=-v:refname | head -1

Master decision tree

Post-setup operations router

Start at the top: answer each gate until you reach a workflow. Open it from the catalog below.

Walk through it

Use the wizard when you want a guided recommendation instead of reading the full map.

Your path on the map

Dimmed branches fade; your choices stay highlighted.

Workflow catalog

Each workflow maps to published pages — drill in for phases, commands, and troubleshooting.

Code	When	Typical time	Go to
Set up a New App	First-time install — vendor ZIP to a live site	Multi-session · 12 phases	Set up a New App
WF-SHIP	Feature, bug fix, or config ready to deploy	15 min – 2 h	Ship → staging → production · Runbook: code → test → ship
WF-SYNC	Server has files not in git (uploads, installer output)	5 – 15 min	Server sync capture · Runbook
WF-UPDATE	CodeCanyon author shipped a new version	1 – 4 h	Vendor updates playbook
WF-HOTFIX	Production broken; you can fix in under an hour	15 min – 1 h	Hotfix forward
WF-ROLLBACK	Production broken; restore last good release now	5 – 15 min	Roll back
WF-SECURITY	composer audit or npm audit found CVEs	30 min – 2 h	Security package update runbook
WF-MODULE	Deploy new or updated ZajModule / package	10 – 30 min	Customizations playbook · Zaj module deploy runbook
WF-DOCS	Create or refresh project documentation	15 – 60 min	Authoring docs runbook

Continuous Deploy is the default loop

Most weeks you only alternate WF-SHIP and occasional WF-SYNC. Vendor updates, hotfix, and security are exception paths — still the same branch model and database gate underneath.

Shared conventions

Branch model

Branch	Purpose	Deploys to
develop	Active development	Local only
staging	Pre-production testing	Staging server
production	Live site	Production server
main	Production backup mirror	—
author/v*	Frozen vendor snapshots	Never deployed

Deep dive: Branch strategy · Version control guide.

Commit types (emoji prefix)

Emoji / type	When
🔨 🟪 T3 Add-Feature	New functionality
🔨 🟪 T3 Edit-Feature	Changed existing feature
🔧 🟦 T2 Fix-Bug	Bug fix
🔧 🟦 T2 Setup-*	Config, brand, security, infra
🚀 🟨/🟩 T4 Deploy-App	After dep deploy staging / production
📦 ⬜ T1 Setup-Author	New vendor import
🔄 ⬛ T5 ServerSync-*	Server capture → git

Standard deploy sequence

Used by WF-SHIP, WF-UPDATE, WF-SECURITY, and WF-MODULE after local work is verified:

git push origin develop
git checkout staging && git merge develop && git push origin staging
dep deploy staging
# Test staging — critical paths

git checkout production && git merge staging && git push origin production
dep deploy production
# Test production — critical paths

git checkout main && git merge production && git push origin main
git checkout develop

WF-HOTFIX is the exception: branch from production, deploy straight to production (skip staging), then back-merge to develop and staging. See Hotfix vs normal deploy.

Database safety gate (pre-deploy)

Run before every deploy that may include migrations:

php artisan migrate:status
php artisan migrate --pretend
# If Atlas is configured:
atlas schema diff --from "$ATLAS_LOCAL_URL" --to "$ATLAS_STAGING_URL" -w
atlas migrate lint --env local --latest 1   # STOP on DS102 (DROP TABLE), DS103 (DROP COLUMN)

Operation	Risk	Action
CREATE TABLE / ADD COLUMN (nullable)	Low	Proceed
ADD COLUMN (NOT NULL) / MODIFY COLUMN	Medium	Staging first
DROP COLUMN / DROP TABLE	High	Backup + explicit approval
TRUNCATE	Critical	Block — manual approval only

Full gate and Atlas workflow: Ship — database safety · Database and migrations guide.

Destructive migrations

Never deploy DROP/TRUNCATE-class changes without a database backup. Code rollback does not undo migrations — see Roll back.

Abort conditions (all workflows)

Stop and reschedule if any of these are true:

• Friday after 3 PM (wait until Monday unless true emergency)
• Destructive migrations without a backup
• Local tests or verification failing
• You are rushing or do not understand the change
• You cannot reach help if something goes wrong

Post-deploy checks (all workflows)

# 1. Site loads + no new errors
curl -sI "https://[DOMAIN]" | head -5
ssh [SSH_PRODUCTION_ALIAS] "tail -20 [DEPLOY_PATH]/storage/logs/laravel.log | grep -i error || true"

# 2. Clear + warm caches, restart queue workers (skip if your Deployer hooks already do this)
ssh [SSH_PRODUCTION_ALIAS] "cd [DEPLOY_PATH] && [PHP_BIN] artisan optimize:clear && [PHP_BIN] artisan optimize"
ssh [SSH_PRODUCTION_ALIAS] "cd [DEPLOY_PATH] && [PHP_BIN] artisan queue:restart"

Then spot-check login, dashboard, and the path you changed. If changes are not visible, purge the Cloudflare cache (dashboard → Purge, or enable Dev Mode).

Related hubs

Collection overview Five playbooks at a glance — setup through hotfix.

Continuous Deploy WF-SHIP + WF-SYNC — the everyday outward/inward loop.

Emergency Hotfix WF-HOTFIX + WF-ROLLBACK when production is broken.

Runbooks shelf Terse command cards when you already know the drill.

Operations cheat sheets Glanceable tables and decision aids.

→Most common next step

Ship — code → test → deploy