WIP: Define native Commons and regional growth contracts #43
Loading…
Reference in a new issue
No description provided.
Delete branch "oss-oo/commons-selfhosting-20261025"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Commons currently depends on the Worker/D1 deployment inherited from shared hosting. This proposal defines a native service on our own infrastructure, with PostgreSQL transactions, durable identities, complete legacy data mapping and a regional growth path.
The plan separates the backend, website and private operations lifecycles. It specifies shared authority locks, recoverable command receipts, outbox limits, compatible rollout, complete write fencing and offsite restore evidence. Host capacity, quorum and replication are explicitly separate; no live PostgreSQL or regional HA capability is claimed.
Validation: the full repository baseline and diff checks pass. Independent architecture review and a second review of the resulting clarifications accept the document as a plan only. Runtime code, native PostgreSQL tests, migration, browser acceptance and production activation remain separate work.
Stacked on the accepted browser-source branch to preserve its documentation context. The existing production Worker continues until a verified replacement is ready. No deployment or Cloudflare plan change is part of this PR.
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.