mirror of
https://github.com/rennf93/roboco.git
synced 2026-08-03 07:23:24 +02:00
Renn F
8e87506da4
The gh-pages branch deploy (mkdocs gh-deploy --force) raced GitHub's built-in branch deployment and got canceled, and each force-push wiped the custom-domain CNAME. Switch to GitHub's official Pages Actions flow (build -> upload-pages-artifact -> deploy-pages) with a single 'pages' concurrency group, so there is one deterministic deployment and no branch to force-push. - Set the custom domain to docs.roboco.dev (site_url + a docs/CNAME that ships in the build artifact, so the domain persists across deploys). - Point the advertised docs URL at https://docs.roboco.dev across README, the usage/deployment stubs, the Makefile help, pyproject, and CLAUDE.md. - Requires a one-time Settings -> Pages -> Source = "GitHub Actions"; the gh-pages branch is no longer used.
926 B
926 B
RoboCo Deployment Guide
This guide has moved. Deploying RoboCo is now documented in the full docs site at docs.roboco.dev (source under
docs/).
Jump straight to:
- Install & first run — the quickest path: clone, set two secrets,
docker compose up. - Deployment — the production guide: compose files, the single-origin nginx, host-path mounts, data persistence, secure mode, and startup ordering.
- Environment reference — every
ROBOCO_*setting with its default and purpose. - Data & migrations — the schema, pgvector, and how the stack self-migrates.
- Troubleshooting — the common deploy snags and their fixes.
Preview the site locally with make serve-docs.