cloudinit-bot
a8ec7b80de
feat(scripts+workflows+docs): explain_run, reclassify, replay, dashboard, daily_digest, operator-tutorial (REQ-INB-42 + -44 + -45 + -50 + -47 + -53)
...
---ci---
project: inboxos
phase: 1
milestone: v1.4
status: execute
wave: 2
tasks: [T3, T4, T5, T6, T7, T8]
---/ci---
2026-06-09 14:19:49 +00:00
034b08ff3e
INB-117: correct documented SeaweedFS bucket and historical .mbox key
...
InboxOS — PR CI / Fast offline tests (pull_request) Successful in 28s
InboxOS — PR CI / 100MB historical e2e (pull_request) Successful in 11m9s
InboxOS — PR CI / Live Ollama extract smoke (pull_request) Successful in 51s
The actual deployment uses bucket 'inboxos' (not 'inboxos-eml') and the
.mbox lives at key 'eml/historical/all-mail.mbox' (not 'historical/all-mail.mbox').
Full canonical URI: s3://inboxos/eml/historical/all-mail.mbox. Confirmed by
Gitea Actions run #922 (probe dispatch on runner-2, 799 MB read, end-to-end
UPSERT into NocoDB).
Updates:
- README.md: add Historical archive section with canonical URI and mc ls hint.
- .env.example: SEAWEEDFS_S3_BUCKET=inboxos.
- docs/operations-runbook.md: §3.2 key example, §4.4 layout header + s3:// URI,
§6.1 secret table, §6 env-var inventory.
- .gitea/workflows/historical-pipeline.yml: comment + workflow_dispatch input.
- .gitea/workflows/live-pipeline.yml: comment.
- pipelines/README.md: live + historical secret blocks.
- scripts/setup_gitea_secrets.sh: SEAWEEDFS_S3_BUCKET default.
- pipelines/historical_pipeline.py + live_pipeline.py: bucket_default kwarg.
INB-34 description also updated to match (doc-text correction; INB-34 itself
is closed done in INB-43 with the correct values).
Test fixtures in pipelines/_tests/ retain the 'inboxos-eml' string as a
self-contained test-only value; the issue explicitly allows this.
Verification:
git grep -n 'inboxos-eml' -- ':!pipelines/_tests/' -> 0 hits
git grep -n 'historical/all-mail.mbox' (no eml/ prefix) -> 0 hits
Refs: INB-34, INB-43 (probe run #922 ), INB-7
Co-Authored-By: Paperclip <noreply@paperclip.ing >
2026-06-08 13:05:41 +00:00
b6224c2313
inb-35: add operations runbook and top-level README
...
- docs/operations-runbook.md: 8-section runbook (system overview,
service inventory, workflow ops, observability, failure modes,
security, cost, glossary) so a new operator can recover from
common failures without re-deriving the architecture.
- README.md: top-level entry point that links to the runbook as
the day-1 incident-response reference.
Co-Authored-By: Paperclip <noreply@paperclip.ing >
2026-06-08 08:23:00 +00:00
cloudinit-bot
cto