Skip to content

Choosing a Deployment Method

This page only helps you choose a path

The complete deployment documentation now lives under Deployment Overview. This page remains as a short entry point so old links and deployment links from the user guide land on the same selection page.

For local use, LAN use, or a temporary trial, go straight to Getting Started.
For long-term operation, a domain name, HTTPS, backup, and upgrades, start from Deployment Overview.

Choose a Runtime First

MethodBest forNext step
DockerNAS devices, home servers, small teams, existing container environmentsDocker Deployment
Docker follower nodeConnecting another AsterDrive instance as a remote storage backendDocker Follower Node
systemdCloud servers, physical machines, long-term stable operationsystemd Deployment
Direct binary runLocal tests and temporary validationGetting Started

For a first deployment, prefer Docker. For long-running Linux servers, prefer systemd.

What to Confirm Before Launch

A production deployment is more than starting a container. Confirm these items first:

  • Data directory: config.toml, the database, and the local upload directory must survive upgrades and restarts
  • Access path: the public entry point should provide HTTPS through a reverse proxy
  • Public site URL: shares, mail, WOPI, and cross-origin access all depend on it
  • WebDAV: if Finder, Windows, rclone, or sync tools will use it, the proxy layer must pass the required methods and upload sizes
  • Storage location: local disk, S3 / MinIO, and follower nodes each have different maintenance costs
  • Backup and restore: verify the backup and restore flow before launch, not after a failure

These topics are covered in order in Deployment Overview. This page only keeps the selection path.

Common Next Steps

Released under the MIT License