Deployment

Deployment Methods

Method 1: Manual Distribution

1. Copy changed files from development to tenants
2. Rebuild affected containers
3. Verify functionality

# Copy specific files
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"
done

# Rebuild all
for tenant in magic_brinxx magic_default magic_logohorloge magic_bovisales magic_demo magic_desluis magic_jodasign magic_spranz; do
  cd "/mnt/data/magic_omniverse/magic_commerce/$tenant"
  docker compose build backend && docker compose up -d backend
done

Note

master_magic is a special tenant used for internal platform management and is not typically included in standard distribution loops.

Method 2: Portal Tenant Manager

Use the Magic Portal at portal.magiceverse.online:

1. Go to Tenant Manager page
2. Select the dev project to deploy
3. Choose target tenants (multi-select)
4. Select components (backend, storefront, or both)
5. Click Deploy — the portal handles copying and rebuilding

Method 3: Beta Server

For the beta/external server at beta.brinxx.nl:

ssh beta-brinxx
cd /var/www/brinxx.nl
docker compose build backend
docker compose up -d backend

Pre-Deployment Checklist

• Changes tested in magic_development
• Dev Project created and changelog updated
• Database migrations checked (if schema changes)
• No hardcoded development URLs in code
• CORS configuration updated if new domains added

Database Migrations

If your changes include database schema modifications:

# Migrations run automatically on container start
# But you can also run manually:
docker exec magic_brinxx_backend_dev npx medusa db:migrate

Rollback

If a deployment fails:

1. Check logs: docker logs magic_{tenant}_backend_dev --tail=100
2. Revert files from a previous version or backup
3. Rebuild: docker compose build backend && docker compose up -d backend

Caution

Always keep a backup of the PostgreSQL database before major deployments. Schema changes cannot be easily rolled back.

Beta Server

Property	Value
URL	beta.brinxx.nl
SSH	ssh beta-brinxx (or ssh ubuntu@37.97.132.23)
Code	/var/www/brinxx.nl/
Images	/mnt/data/pim_data/
DB Password	See Vaultwarden