Table of Contents
🌏 中文版
CapRover is a self-hosted PaaS built on Docker Swarm, with a dashboard and CLI, Nginx, Let's Encrypt, and one-click apps. Applications deploy from source, Dockerfiles, or images, while captain-definition records the build and deployment recipe.
Swarm exists beneath the wrapper
Docker Swarm supplies replicas, placement, service updates, and node failure handling. A cluster adds manager or worker nodes, with Nginx balancing stateless replicas. A simpler UI does not remove manager quorum, overlay network, registry, capacity, OS patching, or upgrade duties.
Push production images to an external registry with immutable references so new nodes, rollback, and recovery do not depend on the build host. Deployments need termination handling, connection draining, compatible migrations, and health—not merely a started container.
Persistent Apps lose scheduling freedom
Persistent Apps mount Docker volumes or host paths so data survives restarts and updates. They become pinned to a server and cannot scale to multiple instances; data does not follow a rescheduled service after node failure.
Keep web and API layers stateless, put uploads in object storage, and use replication-aware databases. A necessary single-node volume needs disk monitoring, off-site backup, and joint data-and-placement restoration. Shared filesystems and plugins introduce their own consistency and failure semantics.
A CapRover backup is not everything
The Backup/Restore feature is documented as experimental. A normal backup preserves control configuration and certificates but excludes container images and persistent directories. Full recovery includes CapRover state, registry images, volumes or databases, DNS, secrets, and node labels.
CapRover fits small teams starting on one VPS and later scaling stateless services with Swarm. Consider Dokploy for Compose and independent remotes, Coolify for a broader resource control plane, and Kubernetes for deeper policy and operator ecosystems. Test worker and manager loss, image reconstruction, volume restore, certificate renewal, and schema-safe rollback.
References
Loading...