Git mirror of a shared folder #52
Labels
No labels
area:docs
area:identity
area:ops
area:plugin
area:server
channel:community
channel:direct
channel:owned
channel:press
channel:social
e2ee-constrained
gate:at-ga
gate:pre-ga
marketing
parity
relay:absent
relay:planned
relay:requested
relay:supported
risk:additive
risk:contract
risk:none
usability
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
Nectenda/nectenda#52
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Part of #37. Depends on the headless client. Must follow Phase 17.
What Relay does
relay-git-sync, a Python Docker service on the Premium tier, subscribes toshared folders over websocket and writes timestamped Git commits. Server-side,
because their server reads plaintext.
What we do
The same outcome, from a headless client holding the customer's keys. Ours can be
self-hosted by the customer without trusting us with anything, which is the
better story — but it is a different deployment shape and the docs must say so.
Sequencing: this cannot precede Phase 17
A Git mirror that cannot serialise a canvas produces a repository that is wrong
in a way nobody notices — which is the failure mode
CLAUDE.mdcalls the worstone, transplanted into a backup. Structured documents must serialise correctly
first.
Risk
risk:additive.Verification
A round trip: sync a folder containing markdown, attachments and a canvas; the
Git tree reproduces all three faithfully.
Moved to the Vikunja board as NEC-29: https://projectron.nerchure.com/tasks/29