Deployment
Deployment Guide
A planned guide for deploying a hosted Dits server, intended to support Docker, Kubernetes, and cloud-managed solutions.
Important
Planned — not yet available.There is no Dits server to deploy today. The API server, storage service, managed cloud (Ditshub), and the container images and Helm charts referenced below are part of the roadmap and have not been built. Dits today is a local-first Rust CLI — there is nothing to host. Treat everything on this page as a design sketch of the intended architecture, not as working deployment instructions.
Deployment Options
Architecture Overview
Core Components
API Server
REST API, authentication, metadata
Storage Service
Chunk storage, deduplication, retrieval
Database
PostgreSQL for metadata, Redis for caching
Worker Queue
Background processing, cleanup, maintenance
Data Flow
→Client uploads file via API
→Storage service chunks and stores
→Metadata saved to database
→Workers handle cleanup and optimization
Prerequisites
Quick Start Deployments
Configuration
Environment Variables
| Variable | Description | Default | Required |
|---|---|---|---|
| DATABASE_URL | PostgreSQL connection string | - | |
| REDIS_URL | Redis connection URL | redis://localhost:6379 | - |
| JWT_SECRET | Secret for JWT token signing | - | |
| STORAGE_TYPE | Storage backend (local, s3, minio) | local | - |
| API_PORT | Port for API server | 8080 | - |
Security Considerations
Monitoring & Maintenance
Health Checks
All services expose health check endpoints at
/health for load balancer monitoring.Key Metrics to Monitor
Backup & Recovery
Backup Strategy
Database Backups
- Daily full backups
- Hourly incremental backups
- Point-in-time recovery
- Encrypted storage
Chunk Storage Backups
- Cross-region replication
- Immutable backups
- Content verification
- Retention policies
Support & Resources
Need Help?
For deployment assistance or enterprise requirements, contact our team or join the community.