Skip to content

Glossary

This page explains terms that appear repeatedly in the AsterDrive documentation. When a concept is unfamiliar, check its meaning here before continuing with the related configuration or workflow.

Nodes and Runtime Modes

TermMeaningRelated docs
Primary node / primaryThe default runtime mode. It handles login, frontend, admin console, shares, WebDAV, policies, and metadata.Server Configuration
Follower node / followerA remote storage backend. It only accepts internal object requests signed by the primary node and does not let regular users log in.Follower Nodes
Remote nodeA follower record registered in the primary admin console, including node address, status, secrets, and ingress target.Follower Nodes
Ingress targetThe real place where a follower writes objects, either a local directory or S3 / MinIO.Follower Nodes
enrollThe action that binds a follower to the primary. Usually, the admin console generates a command and you run it on the follower.Operations CLI

Storage and Uploads

TermMeaningRelated docs
Storage policyDefines where files actually land and how uploads are performed, such as a local directory, S3 / MinIO, or a follower node.Storage Policies
Policy groupDecides which storage policy a user or team hits during upload. It can route by file size.Storage Policies
BlobThe underlying file object. Multiple file records can reference one blob for content deduplication and version references.About AsterDrive
Chunked uploadSplits a large file into multiple chunks and tries to resume after failure.Uploads and Large Files
Direct-to-object-storage uploadThe browser uploads directly to S3 / MinIO; the server only signs requests and confirms completion.Uploads and Large Files
Server relayThe browser uploads to AsterDrive first, then the server writes to S3 / MinIO.Uploads and Large Files

Configuration

TermMeaningRelated docs
config.tomlStartup configuration. It controls listen address, database, logging, WebDAV prefix, node mode, and similar startup-level behavior.Configuration Overview
System settingsSite-wide rules changed live from the admin console, including public site URLs, registration, cookies, mail, trash, WOPI, and audit logs.System Settings
Public site URLThe externally reachable HTTP(S) origin of AsterDrive, used for shares, mail, WebDAV, WOPI callbacks, and more.System Settings
CORSBrowser cross-origin access rules. Only allow origins when you explicitly need cross-origin API calls.System Settings
Reverse proxyThe public entry point such as Caddy, Nginx, or Traefik, responsible for HTTPS, domains, upload sizes, and passing WebDAV methods.Reverse Proxy

Access Protocols and External Services

TermMeaningRelated docs
WebDAVLets Finder, Windows, rclone, or sync tools access AsterDrive through a file protocol.WebDAV
WOPIThe Office online preview/editing protocol. AsterDrive provides file APIs while OnlyOffice / Collabora and similar services open the files.File Editing
Preview appA file open method configured in the admin console. It can be a built-in preview, an external URL template, or a WOPI app.System Settings
Audit logRecords important user and admin actions for troubleshooting, tracing, and routine checks.Admin Console

Operations

TermMeaningRelated docs
doctorOperations CLI subcommand for deployment checks, configuration checks, and deep consistency checks.Operations CLI
Database migrationMoves business data from one database backend to another, such as SQLite to PostgreSQL.Operations CLI
Frontend asset cacheA common cause of broken pages after upgrades, when a browser or proxy caches old page assets.Frontend Asset Cache
RollbackReturning to an old version after a failed upgrade, usually with the old binary/image and pre-upgrade backups.Upgrades and Version Migration

Released under the MIT License