One VPS, Docker, automatic HTTPS.
API + workers + Redis queue + SearXNG, fronted by Caddy with automatic TLS.
Pushes to dev redeploy staging; production ships on manual dispatch
after CI passes. Every deploy is health-gated with automatic rollback.
# staging (plain HTTP, isolated data) /opt/openbotics-staging/.env → OPENBOTICS_MONGO_DB=openbot_staging # production (TLS via Caddy) /opt/openbotics/.env → OPENBOTICS_MONGO_DB=openbot
prev-* on the server..env or vault files.Set OPENBOTICS_PUBLIC_URL to your public origin and register
{PUBLIC_URL}/api/plugins/<id>/oauth/callback with each provider.
The repo's docs/ holds the complete pipeline, VPS, and Electron
runbooks: cicd.md, deploy-vps.md, dev-pipeline.md.