Installation Overview
RepoFlow supports a few installation options, each optimized for a different kind of environment. This page helps you choose the right one.
Quick recommendation
- Production on Kubernetes: Use Helm for high availability, scaling, and long-running environments.
- Production on a single server: Use Docker Compose for a simpler deployment with separate services.
- Personal use or testing on a Synology NAS: Use the Synology SPK from the RepoFlow package source.
- Personal use or local testing: Use the Docker all-in-one container for the quickest setup.
Caution: Choose your deployment type up front. Switching deployment types later is not supported and usually requires a fresh deployment and a careful data migration plan. If you still need to switch, please contact support.
Compare options
| Option | Best for | Tradeoffs | Docs |
|---|---|---|---|
| Helm chart (Kubernetes) | Production, HA, scaling | Requires a Kubernetes cluster and Helm | Deploying with Helm |
| Docker Compose | Production on a single server | Simpler than Kubernetes, with limited built-in HA | Deploying with Docker Compose |
| Synology NAS (SPK) | Personal use or testing on a compatible Synology NAS | Requires Container Manager and the RepoFlow package source | Deploying on Synology NAS |
| Docker (all-in-one container) | Personal use or local testing | Everything runs in one container and is not designed for production or HA | Deploying with Docker |
How to choose
Pick based on where you’re running RepoFlow:
- Production with Kubernetes: use Helm.
- Production on one server: use Docker Compose.
- Personal use or testing on Synology: use the Synology SPK.
- Personal use or local testing: use Docker all-in-one.
Air‑gapped environments
If your environment has no internet access:
- Helm: Air‑gapped deployment (Helm)
- Docker Compose: Air‑gapped deployment (Docker Compose)