Deployment¶
Kamerplanter can be operated in different ways — from a single docker compose up on your own machine to a fully managed Kubernetes cluster.
Which method is right for you?¶
| Scenario | Recommended method |
|---|---|
| Trying it out, single user, home network | Docker Compose Quick Start |
| Permanent operation on Raspberry Pi / NAS | Docker Compose Permanent Operation |
| Multiple users, high availability, professional use | Kubernetes + Helm / ArgoCD |
Set the mandatory secrets before every rollout
Regardless of the path you choose, the backend refuses to start once DEBUG=false is set and JWT_SECRET_KEY, FERNET_KEY, or ERASURE_TOMBSTONE_SALT is missing. Every deployment page in this section shows where these values belong — the complete reference lives in the Configuration Matrix.
In this section¶
Docker Compose¶
- Docker Installation — Set up Docker on Windows, macOS, Linux, or Raspberry Pi
- Docker Compose Quick Start — Up and running in 5 minutes
- Docker Compose Permanent Operation — Updates, backups, and access from other devices
Kubernetes¶
- Deployment Profiles — Which components do I need? Comparing Minimal to SaaS
- Configuration Matrix — Exhaustive reference of every feature with its switch, mandatory secrets, and resource impact
- Kubernetes — Cluster prerequisites and deploying Kamerplanter
- Helm Charts — Chart structure, configuration, and customization
- ArgoCD — GitOps-based deployment
- CI/CD — Automated builds and deployments with GitHub Actions
- Setting Up Image Recognition — Self-hosted plant image recognition (optional)
- Environment Variables — Complete variable reference