cloudinit-bot
349b59a4ab
The v1.1 P0 sweep (commits7c20d5d,d530921) updated the 3 new shell helpers, the runbook, and 2 runbook lines to point at jc-capital. It missed 2 files: - docs/gitea-actions.md:95 (last touched at Phase 4 / INB-33, before the v1.0→v1.1 org migration; the v1.1 sweep was scoped to .md / .sh created or modified in v1.1) - scripts/setup_gitea_secrets.sh:4,14,18,28 (pre-existing at the v1.0 close; not in the v1.1 diff; filed as v1.1 P1-2 for v1.2 follow-up but v1.2 was a 0/1 disposition so the carry-forward is v1.3) This commit closes the cto-inboxos owner drift in both files using the same env-var-resolved default pattern as the v1.1 P0 sweep: - docs/gitea-actions.md:95 now uses ${GITEA_OWNER:-jc-capital}/inboxos - scripts/setup_gitea_secrets.sh:4,14 use the same ${GITEA_OWNER:-jc-capital} pattern in the header - scripts/setup_gitea_secrets.sh:18 defaults GITEA_OWNER to jc-capital - scripts/setup_gitea_secrets.sh:28 uses ${GITEA_OWNER:-jc-capital} in the example Verified: grep -n cto-inboxos docs/gitea-actions.md scripts/setup_gitea_secrets.sh returns empty. The script is still chmod +x with set -euo pipefail (unchanged). This commit also closes v1.1 backlog item P1-2 (setup_gitea_secrets.sh owner drift, per CI-LOG.md:219-220). ---ci--- project: inboxos phase: 1 milestone: v1.3 status: execute tasks_completed: [T1.1] candidates_closed: [REQ-INB-28, REQ-INB-37] backlog_closures: v1_1_P1_2: REQ-INB-37 files_touched: - docs/gitea-actions.md (1 line, line 95) - scripts/setup_gitea_secrets.sh (4 lines, 4, 14, 18, 28) ---/ci---
InboxOS
Self-hosted personal ERP / CRM pipeline. A single Gmail inbox, polled over IMAP, archived to SeaweedFS, classified and extracted by a local LLM (Ollama), and written to NocoDB as structured records. Curated attachments are mirrored to Papra. No third-party SaaS touches PII.
Where to start
- Operations runbook —
docs/operations-runbook.md. System overview, service inventory, workflow operations, observability, failure modes, security, cost, glossary. The first thing to read on day 1 of incident response. - Extraction contract —
docs/extraction-contract.md. How a raw email becomes a NocoDB record. Source of truth for theinboxos:classify+inboxos:extract-<module>prompt family. - NocoDB schema —
docs/schemas.md. The four module tables (finance,crm,intel,promotions) and the Message-ID idempotency contract. - Gitea Actions setup —
docs/gitea-actions.md. Runner provisioning (including the second runner for live + historical parallelism), repo secrets, the Basic Auth model. - Pipelines —
pipelines/README.md. Flow diagrams, idempotency model, rollback procedure for the live and historical pipelines. - Papra write policy —
docs/papra-write-policy.md. When the pipeline writes to Papra (attachments + selected bodies), and why the first ship is dry-run.
Quick layout
inboxos/
├── README.md # this file
├── .env.example # placeholder env (no real secrets)
├── docker/
│ └── docker-compose.yml # self-hosted stack: gitea, runners, nocodb, seaweedfs, papra, ollama
├── .gitea/workflows/
│ ├── live-pipeline.yml # cron */5 * * * *, polls IMAP
│ ├── historical-pipeline.yml # workflow_dispatch, streams .mbox
│ └── ci-pr.yml # fast-tests + 100MB e2e + live Ollama smoke
├── pipelines/ # shared Python: common.py, live_pipeline.py, historical_pipeline.py, mbox_stream.py
├── .opencode/commands/ # version-controlled extraction prompts (prompt-as-code)
├── config/ # n8n config (legacy, no longer in use)
└── docs/ # this runbook + schemas + contracts + reports
Status
Phase 5 — Full Deployment. Parent goal: INB-1. Current phase issue: INB-7. The runbook in docs/operations-runbook.md is the canonical reference for ongoing operation.
Historical archive (Google Takeout .mbox)
The full Google Takeout .mbox export lives in SeaweedFS at the canonical S3 URI:
s3://inboxos/eml/historical/all-mail.mbox
That is the value to pass as the mbox_object_key workflow_dispatch input to historical-pipeline.yml. To verify it exists, run from any host with mc configured against the inboxos bucket:
mc ls --recursive inboxos/inboxos/ | grep '\.mbox$'
The historical pipeline streams this object message-by-message, UPSERTs each into NocoDB on Message-ID, and writes the raw .eml backup under s3://inboxos/eml/historical/<yyyy>/<mm>/<dd>/<Message-ID>.eml. See docs/operations-runbook.md §3.2 for the dispatch recipe and §4.4 for the full bucket layout.