Upload Archive Deployment
Overview
The Deploy Application flow allows you to configure and launch your application in a few simple steps.
Steps included:
- Source
- Build
- Resources
- Review
Step 1: Basic Information & 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 your application as a compressed source or pre-built binary artifact:
- Supported Formats:
.zip,.tar,.tar.gz,.tgz,.tar.bz2 - File Size Limits: Up to 250 MB via browser direct drag-and-drop; up to 2 GB when using presigned object storage URLs (S3, Cloudflare R2, GCS)
- Integrity Verification: Automated SHA-256 checksum scan upon upload completion
Drag-and-Drop Dropzone & Remote URL:
- Direct Upload: Drag your archive directly into the active dashed dropzone or click Browse Files.
- Remote Archive URL: Paste an authenticated HTTPS URL or presigned S3 object link to pull large archives directly into the Nife build runner.
- Root Directory Constraints: Ensure your entrypoint file (
Dockerfile,package.json,requirements.txt, orindex.html) resides in the archive root or configure the custom sub-directory in Step 2.
Step 2: 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

Optimize your image to:
- Reduce size
- Improve startup time
- Remove unnecessary layers
- Lower storage cost
Ready to Build

Click Start Build to begin building your container image.
Build Success

After build:
- Image is created successfully
- Logs show build steps
- Image is tagged and stored
Step 3: Resources
Resource Selection

Choose compute type:
- CPU
- GPU
- TPU
- Serverless
- Edge AI
Resource Requests & 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

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

Persistent Volume:
- Attach storage to container
- Define:
- Size (GB)
- Mount Path (e.g., /data)
Scaling:
- Replicas per region (1–10)
Step 4: Review

Before deploying, review:
- App name
- Source
- CPU & Memory
- Replicas
- Ports
- Volume
- Regions
Related Resources
- 📁 FileHost — Nife's simple file sharing service for sharing build artifacts
- 🚀 Launch Dashboard — Deploy your app on Nife