bsodfather/crank
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

ci: load deploy secrets from openbao
CI / Rust Checks (push) Has been cancelled
Details
CI / UI Checks (push) Has been cancelled
Details
CI / Frontend E2E (push) Has been cancelled
Details
CI / Deployment Manifests (push) Has been cancelled
Details
Deploy / build-images (apps/admin-api/Dockerfile, git.itexp.me/bsodfather/crank-community-admin-api, admin-api) (push) Has been cancelled
Details
Deploy / build-images (apps/mcp-server/Dockerfile, git.itexp.me/bsodfather/crank-community-mcp-server, mcp-server) (push) Has been cancelled
Details
Deploy / build-images (apps/ui/Dockerfile, git.itexp.me/bsodfather/crank-community-ui, ui) (push) Has been cancelled
Details
Deploy / deploy (push) Has been cancelled
Details

Browse Source
This commit is contained in:
github-ops
2026-06-16 14:55:28 +00:00
parent 15d7cfa8d9
commit 1bb16cde09
8 changed files with 165 additions and 57 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/runtime-config.md
+5 -4
View File
@@ -235,11 +235,12 @@ Demo/deployment:
В deployment workflow больше не используется монолитный `DEPLOY_ENV_FILE`.
`.env` на сервере собирается из отдельных GitHub secrets, причем имя секрета совпадает с именем
runtime env-переменной. Это значит, что:
`.env` на сервере собирается из OpenBao. В Gitea Actions хранятся только bootstrap credentials
`BAO_ADDR`, `BAO_TOKEN` и `BAO_SECRET_PATH`, а внутри OpenBao ключи совпадают с именами
runtime env-переменных. Это значит, что:
- `CRANK_MASTER_KEY` хранится как GitHub secret `CRANK_MASTER_KEY`;
- `CRANK_DEMO_SEED` хранится как GitHub secret `CRANK_DEMO_SEED`;
- `CRANK_MASTER_KEY` хранится в OpenBao как ключ `CRANK_MASTER_KEY`;
- `CRANK_DEMO_SEED` хранится в OpenBao как ключ `CRANK_DEMO_SEED`;
- и так же для остальных runtime-переменных.
Для БД основной runtime-контракт теперь компонентный: