Syncs Gmail to a local OSIS instance for Hero OS.
- Rust 97.4%
- Shell 1.3%
- Makefile 1.3%
despiegk
049c512b90
- Independent concurrent syncing: replace the single global running flag with per-domain DomainGuards (gmail/contacts/calendar). Each domain syncs in its own background task against its own store; sync_all fans out concurrently and returns a per-domain ack. Fixes the prior bug where an all-run wrote contacts/calendar into the gmail DB. - Expose body_html/is_html/html_link on the Message rootobject so the HTML email body (already stored in the DB) flows through message_list_full to the UI; map the fields through the row<->struct helpers. - Restore resync_gmail/resync_contacts/resync_calendar (wipe + clear cursor + full re-fetch) and purge_stale_calendar_events. - Ignore .claude/ (agent worktrees/session state); drop a stale worktree gitlink that caused lab build to build every binary twice. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> |
||
|---|---|---|
| crates | ||
| steps | ||
| .gitignore | ||
| Cargo.toml | ||
| Cargo.toml.hero_builder_backup | ||
| CLAUDE.md | ||
| Makefile | ||
| README.md | ||
| rust-toolchain.toml | ||
hero_sync_gmail
Gmail synchronisation service for the Hero ecosystem. Syncs Gmail messages and exposes them via a JSON-RPC API over Unix domain sockets.
Components
| Crate | Role | Port | Socket |
|---|---|---|---|
hero_sync_gmail_server |
JSON-RPC daemon | 3745 | $PATH_SOCKETS/hero_sync_gmail/rpc.sock |
hero_sync_gmail_admin |
Admin dashboard | 3746 | $PATH_SOCKETS/hero_sync_gmail/admin.sock |
hero_sync_gmail_cli |
CLI client | — | — |
hero_sync_gmail_sdk |
Generated typed client | — | — |
hero_sync_gmail_app |
Dioxus web frontend | 3647 (dev) | $PATH_SOCKETS/hero_sync_gmail_app/web_app.sock |
Prerequisites
# Rust 1.96 (stable)
rustup show
# For the Dioxus frontend only:
rustup target add wasm32-unknown-unknown
cargo install dioxus-cli --locked
Quick Start
Open separate terminals for each component.
# Terminal 1 — server
make server
# Terminal 2 — admin dashboard
make admin
# Terminal 3 — CLI
make cli ARGS="ping"
make cli ARGS="sync"
make cli ARGS="status"
# Terminal 4 — Dioxus frontend (requires dx CLI)
make app
Build
make build # cargo build --release --workspace
make check # cargo check --workspace
make test # cargo test --workspace
Smoke Testing (server must be running)
# Health check
curl --unix-socket "$PATH_SOCKETS/hero_sync_gmail/rpc.sock" http://localhost/health
# OpenRPC spec
curl --unix-socket "$PATH_SOCKETS/hero_sync_gmail/rpc.sock" http://localhost/openrpc.json
# Ping via RPC
curl --unix-socket "$PATH_SOCKETS/hero_sync_gmail/rpc.sock" \
-X POST http://localhost/rpc \
-H 'Content-Type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"gmail_sync_service.ping"}'
# Or via TCP (port 3745)
curl -s -X POST http://localhost:3745/rpc \
-H 'Content-Type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"gmail_sync_service.ping"}'
Service Manifests
Each binary crate embeds a service.toml at its crate root and answers --info:
make server-info # hero_sync_gmail_server --info --json
make admin-info # hero_sync_gmail_admin --info --json
make cli-info # hero_sync_gmail_cli --info --json
Architecture
The server uses the oschema-first pipeline:
oschema/main/gmail.oschema
│
│ openrpc_server!(spec = "oschema", service_toml = "service.toml")
▼
pub mod main ← GmailSyncServiceApi trait + all Input/Output types
serve_domains(impl) ← mounts rpc.sock + TCP 3745
│
└── $PATH_SOCKETS/hero_sync_gmail/rpc.sock
The schema defines a Message rootobject (auto-generates 8 CRUD methods) and a GmailSyncService block with ping, sync, and status custom methods.
The SDK (hero_sync_gmail_sdk) is generated from openrpc/openrpc_main.json via openrpc_client! after the server is built.
Validation
lab infocheck # validates all binary crates in this repo