Skip to main content

Upload Archive

Overview​

The Deploy Application flow allows you to configure and launch your application in a few simple steps.

Steps included:

  1. Source
  2. Build
  3. Resources
  4. Review

Step 1: Basic Information & Source​

Basic Info & Source

Fill the following details:​

  • Organization – Select your organization
  • Workload Environment – Choose or create one
  • Application Name – Unique name for your app

Upload Archive​

Upload Archive

Upload your application as a compressed file:

  • Supported formats: .zip, .tar, .tar.gz
  • Max size: 100MB

Options:​

  • Upload file (drag & drop)
  • Paste Archive URL (e.g., S3 link)

Step 2: Build Configuration​

Build Configuration

Available Options:​

  • Auto-Dockerize with Runtime
    Automatically generates a Dockerfile

  • Add Custom Dockerfile
    Upload or write your own

  • Specify Dockerfile Path
    Use an existing Dockerfile

If no option is selected, the platform auto-detects your app.

Docker Image Optimization​

Docker Optimizer

Optimize your image to:

  • Reduce size
  • Improve startup time
  • Remove unnecessary layers
  • Lower storage cost

Ready to Build​

Ready to Build

Click Start Build to begin building your container image.

Build Success​

Build Logs

After build:

  • Image is created successfully
  • Logs show build steps
  • Image is tagged and stored

Step 3: Resources​

Resource Selection​

Resources Selection

Choose compute type:

  • CPU
  • GPU
  • TPU
  • Serverless
  • Edge AI

Resource Requests & Limits​

Resource Limits

Configure:

  • CPU (Request & Limit)
  • Memory (Request & Limit)

Deployment Strategy​

Choose how updates are deployed:

  • Rolling (recommended)
  • Blue-Green
  • Canary
  • Recreate

Workload Type​

  • Deployment
  • CronJob
  • StatefulSet

Ports & Environment Variables​

Ports & Env

Configure:​

  • Internal Port – Container port (e.g., 3000)
  • External Port – Public access port (e.g., 80)

Environment Variables:​

  • Add key-value pairs
  • Used for configs, secrets, APIs

Volume & Scaling​

Volume & Scaling

Persistent Volume:​

  • Attach storage to container
  • Define:
    • Size (GB)
    • Mount Path (e.g., /data)

Scaling:​

  • Replicas per region (1–10)

Step 4: Review​

Review Summary

Before deploying, review:

  • App name
  • Source
  • CPU & Memory
  • Replicas
  • Ports
  • Volume
  • Regions