Appearance
Cross-repository communication
TODO: One paragraph: how the parts of Ediky talk to each other (HTTP, files, packages, scheduled jobs, IPC), and where each contract is defined.
Communication map
TODO: Replace with the real map. Label every arrow with its protocol.
rendering diagram…
drag to pan · ctrl / ⌘ + scroll to zoom
Channels
| From | To | Channel | Contract | Auth | Docs |
|---|---|---|---|---|---|
| TODO | TODO | TODO: HTTP / IPC / files / package / cron | TODO | TODO | TODO: link to API page |
Contracts
TODO: For each channel, where the contract (request/response shape, file format, package API) is defined, and how breaking changes are handled.
TODO: Contract name
| Field | Value |
|---|---|
| Producer | TODO |
| Consumers | TODO |
| Format | TODO |
| Defined in | TODO: path |
| Versioning | TODO |
Failure handling
TODO: Timeouts, retries, fallbacks and what the user sees when a channel is down.
Security
TODO: Tokens and secrets used across repositories, where they are stored, and what each one can access.