Security update: Docker images from v0.4.0-rc.1 fix the high-severity FFmpeg MagicYUV decoder vulnerability (CVE-2026-8461). Upgrade instances using older images immediately.View CVE advisory
Security update: v0.4.0-beta.3 fixes a WebDAV request issue that can terminate the server process. Upgrade older instances promptly.View advisory
Choose a Deployment
For local, intranet, or temporary trials, skip the choosing and go straight to Quick Start.
Choose by Scale
Section titled “Choose by Scale”| Your scale | Recommended path | Scenario page |
|---|---|---|
| Local trial, temporary evaluation | Run the official image directly; plain HTTP is fine | Quick Start |
| Personal, family, or small-team single instance | Docker Compose or systemd | Single-Instance Docker, Single-Instance systemd |
| Many users, need multiple Primaries for traffic | cluster profile + load balancing | Multi-Instance and Load Balancing |
| Already have a Kubernetes platform | Reuse the repository’s built-in manifests | Kubernetes Deployment |
| Want to attach another AsterDrive as remote storage | Keep the primary; run a follower on the new machine | Follower Storage Node |
For a first deployment, prefer Docker. For long-term Linux servers, prefer systemd. Multiple Primaries are not “two copies of a single instance” — read the contract in Multi-Instance and Load Balancing first.
Choose by Environment
Section titled “Choose by Environment”| Environment | Also read |
|---|---|
| Any production public entry | Reverse Proxy: HTTPS, upload size, WebDAV method passthrough |
| Follower on another network | Follower Node Network Topologies: public internet, VPN, Docker network, or reverse tunnel |
| Object storage (S3 / MinIO / R2 / COS / Azure / OneDrive / SFTP) | The matching tutorial in Storage Backends, connected after deployment |
Confirm Before Launch
Section titled “Confirm Before Launch”A production deployment is more than starting a container. Confirm these ahead of time:
- Data directory:
config.toml, the database, and local upload directories must survive upgrades and restarts - Access method: the public entry should provide HTTPS through a reverse proxy
- Public site URL: sharing, mail, WOPI, and cross-origin access all depend on it
- WebDAV: if Finder, Windows, rclone, or sync tools will connect, the proxy layer must allow the corresponding methods and upload sizes
- Storage location: different storage policy backends have different maintenance costs
- Backup and restore: confirm the backup and restore flow before launch instead of improvising after a failure
After Deployment
Section titled “After Deployment”- What startup completed automatically and what to validate immediately -> First-Start Checklist
- The full pre-launch list -> Production Launch Checklist
- Backup and restore -> Backup and Restore
- Version upgrades -> Upgrade and Version Migration