docs: remote management API + control-plane HA proposals (issue #1)#18
Open
nechodom wants to merge 1 commit into
Open
docs: remote management API + control-plane HA proposals (issue #1)#18nechodom wants to merge 1 commit into
nechodom wants to merge 1 commit into
Conversation
Response to issue #1 follow-up (@LaAlexita) asking for a remote-management API and a high-availability option. Two grounded design docs: - remote-management-api: /api/v1 HTTP/JSON over the existing typed RPC, authed by capability-scoped API keys (reuses the RBAC CapSet + per-mutation gates + background-job model + audit chain). Phased; Phase 1 = keys + core hosting lifecycle. - ha-control-plane: reframes HA as control-plane (hosted sites already survive a master outage), recommends warm-standby + Litestream->S3 replication + master- identity reuse (cert-pinning), with Postgres active-active as the end-state. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Design proposals responding to @LaAlexita's follow-up on issue #1 (remote-management API + high-availability option). No code — two grounded specs to plan from.
remote-management-api-design.md— a/api/v1HTTP/JSON edge over the existing typed RPC (~195 methods), authed by capability-scoped API keys that reuse the RBACCapSet(so the per-mutation gates hardened in the security audit apply unchanged), with background-job polling + audit. Phased; Phase 1 = keys UI + core hosting lifecycle. (Phase-1 build follows in a separate PR.)ha-control-plane-design.md— reframes HA as control-plane (hosted sites already survive a master outage — nginx/PHP run on the workers), recommends warm-standby + Litestream→S3 replication + master-identity reuse (cert-pinning), with Postgres active-active as the end-state.Both end with open questions for you.
🤖 Generated with Claude Code