Code Distribution

Overview

magic_development is the master codebase. All code changes are made here first, tested, then distributed to the other 7+ tenants.

Workflow

Develop in magic_development

cd /mnt/data/magic_omniverse/magic_commerce/magic_development/backend/
# Edit files in src/

Rebuild and test

cd /mnt/data/magic_omniverse/magic_commerce/magic_development
docker compose build backend
docker compose up -d backend

Verify at https://admin-development.magiceverse.online

Distribute to other tenants

src="/mnt/data/magic_omniverse/magic_commerce/magic_development/backend/src"
for tenant in magic_brinxx magic_default magic_logohorloge magic_bovisales magic_demo magic_desluis magic_jodasign magic_spranz; do
  dst="/mnt/data/magic_omniverse/magic_commerce/$tenant/backend/src"
  cp -r "$src/api/admin/aplt/your-changed-route/" "$dst/api/admin/aplt/your-changed-route/"
done

Rebuild affected tenants

cd /mnt/data/magic_omniverse/magic_commerce/magic_brinxx
docker compose build backend
docker compose up -d backend

Examples

Deploy a PDF fix to all tenants

src="/mnt/data/magic_omniverse/magic_commerce/magic_development/backend/src/api/admin/aplt"
for tenant in magic_brinxx magic_default magic_logohorloge magic_bovisales magic_demo magic_desluis magic_jodasign magic_spranz; do
  dst="/mnt/data/magic_omniverse/magic_commerce/$tenant/backend/src/api/admin/aplt"
  cp "$src/orders/pdf/route.ts" "$dst/orders/pdf/route.ts"
  cp "$src/quotations/pdf/route.ts" "$dst/quotations/pdf/route.ts"
done

Rebuild all backends

for d in /mnt/data/magic_omniverse/magic_commerce/*/; do
  cd "$d" && docker compose build backend && docker compose up -d backend
done

Each tenant has its own unique design, branding, and theme. Copying storefront files between tenants will overwrite their design. This has happened before — all tenants received the Brinxx design by mistake.

Forbidden commands:

# NEVER DO THIS:
rsync -av storefront/ target/storefront/
cp -r magic_development/storefront/ magic_brinxx/storefront/

See CLAUDE.md & Sync Guardrails for complete rules.

Dev Projects Tracking

Use the Dev Projects system to track changes:

# Create project
curl -X POST "https://admin-development.magiceverse.online/admin/dev-projects" \
  -H "Content-Type: application/json" \
  -d '{"name": "PDF Fix", "project_type": "bugfix"}'

# Track files
curl -X POST "https://admin-development.magiceverse.online/admin/dev-projects/files" \
  -H "Content-Type: application/json" \
  -d '{"project_id": 1, "files": [{"file_path": "src/api/admin/aplt/orders/pdf/route.ts", "change_type": "modified"}]}'

# Log change
curl -X POST "https://admin-development.magiceverse.online/admin/dev-projects/changelog" \
  -H "Content-Type: application/json" \
  -d '{"project_id": 1, "action": "fix", "description": "Fixed PDF generation", "changed_by": "developer"}'

Git Integration

Dev Projects creates git branches:

Branch pattern: dev-project/{projectCode}
Repository root: /mnt/data/magic_omniverse/magic_commerce/magic_development
Commits logged with “Dev Projects Bot” author