hiveops-guide

T

johannes 37a1c4e396 ci(guide): auto build + deploy to bcos.dev on push to develop (#5 )

The guide bundles content into the backend jar at build time, so instances must be rebuilt +
redeployed to pick up doc changes (git-pull is insufficient). Automates it: on push to develop
(backend/** paths), mvn package -> docker build -> push :dev -> deploy to bcos.dev -> smoke.

mvn package runs FIRST (the Dockerfile COPYs a pre-built jar — skipping it ships stale content).
Auto-deploy scoped to dev only (docs, low risk). Audience filtering is runtime via
GUIDE_SERVED_AUDIENCES, so no build-time filtering — prod (future cd-main, gated) serves
customer,internal only.

Needs (coordinate w/ CI/runner session): BCOS_DEV_DEPLOY_KEY secret + runner reachability to .251.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

2026-07-05 13:10:34 -04:00

.gitea/workflows

ci(guide): auto build + deploy to bcos.dev on push to develop (#5 )

2026-07-05 13:10:34 -04:00

backend

docs(guide): add milestone release history (pre-pilot → pilot → production)

2026-07-05 12:47:10 -04:00

frontend

docs(guide): add platform.production-checks + new DEVOPS section (backups, security)

2026-07-02 07:55:49 -04:00

scripts

docs(guide): add platform.production-checks + new DEVOPS section (backups, security)