Skip to content

storage: redis network backend — multi-machine (messages + team/run state) #208

Description

@fujibee

Part of #51 (1.1.2, deferred). First network backend = beyond local: not just messages but team registry and run state (locks/watermarks/pidfiles) must move to the network. storage_check needs a <500ms connect timeout + local fallback so a stalled redis can't hang agmsg. Significantly larger than the file drivers — scoped to 1.1.2 as its own effort. Acceptance: TBD (depends on how much local-state goes network).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions