Deployments Overview

Urumi uses a three-environment deployment model to ensure your changes are tested before going live. This guide explains how deployments work and best practices for managing your store environments.

Environment Model

Every Urumi store has three environments:

Environment	Purpose	URL Pattern
Development	Active development and coding	yourstore-staging.myscalablesite.com
QA	Quality assurance and testing	yourstore-preview.myscalablesite.com
Production	Live customer-facing site	yourstore-production.myscalablesite.com or your custom domain

Deployment Flow

Changes flow through your environments in this order:

Production → Development → QA → Production
     ↑                              │
     └──────────────────────────────┘

Typical Workflow

1. Pull from Production - Start by copying production content to Development
2. Make Changes - Edit files, add products, configure settings in Development
3. Push to QA - Merge your changes to QA for testing
4. Test in QA - Verify everything works as expected
5. Push to Production - Deploy tested changes to your live site

Key Concepts

Immutable Production Deployments

Production deployments are immutable, meaning once deployed, the code cannot be changed directly. This ensures:

• Consistent, reproducible deployments
• Easy rollback if issues occur
• Audit trail of all changes

Horizontal Scaling

Production environments automatically scale horizontally with traffic. This means your store can:

• Handle traffic spikes during sales and promotions
• Scale to support millions of orders
• Maintain fast response times under high load

You don't need to configure or manage scaling - it happens automatically based on demand.

Environment Isolation

Each environment is completely isolated:

• Separate databases
• Independent file systems
• Different URLs and configurations

Development Best Practice

Always make and test changes in Development before deploying. Never edit production directly.

Accessing the Deploy Tab

1. Navigate to your store from the dashboard
2. Click the Deploy tab in the sidebar
3. You'll see three environment cards showing current status

What Happens During Deployment

When you trigger a deployment:

1. Preparation - Files and database are prepared for transfer
2. Synchronization - Changes are copied to the target environment
3. Verification - Deployment is verified for completeness
4. Completion - AI generates a summary of changes (for certain deployments)

Deployment times vary based on the amount of content being transferred, but typically complete within 1-5 minutes.