0 Fork 0

mirror of https://github.com/spacedriveapp/spacedrive.git synced 2026-11-03 22:05:11 -05:00

Files

T

Jamie Pineandcapy-ai-staging[bot] a2831ac9b2 Run the pairing suites in CI: device persistence, proxy pairing, and relay pairing through a local relay (#3152 )

* Run the pairing suites in CI with condition waits and a local relay

Co-authored-by: capy-ai-staging[bot] <305915985+capy-ai-staging[bot]@users.noreply.github.com>

* Say what the integration group's wall-time budget is and which relay the mDNS suites still reach

Co-authored-by: capy-ai-staging[bot] <305915985+capy-ai-staging[bot]@users.noreply.github.com>

* Name where the integration group's 15 minute target comes from

Co-authored-by: capy-ai-staging[bot] <305915985+capy-ai-staging[bot]@users.noreply.github.com>

* Keep a newer same-ALPN connection alive when an older one to the same node closes

The connection map is keyed by node and ALPN, so an incoming pairing
connection and an outbound one opened for a single message share a key.
When the older one closed, the handler and the per-node watcher removed
the key and took the newer connection's last handle, so QUIC closed it
under the peer before the message had been read. Carol's proxy acceptance
to Alice was lost this way in 1 of 13 proxy_pairing_test runs in sequence.
Removal now checks the stored connection is the closed one, and a one-shot
send waits for the peer to acknowledge the bytes before returning.

Co-authored-by: capy-ai-staging[bot] <305915985+capy-ai-staging[bot]@users.noreply.github.com>

* Wait for the message acknowledgement off the event loop and say when a closed connection's key is kept

Co-authored-by: capy-ai-staging[bot] <305915985+capy-ai-staging[bot]@users.noreply.github.com>

---------

Co-authored-by: capy-ai-staging[bot] <305915985+capy-ai-staging[bot]@users.noreply.github.com>

2026-10-09 12:17:23 +00:00

app

Docs, register, and interface polish from parallel sessions

2026-09-15 17:09:40 -07:00

README.md

Spacedrive Documentation

The Spacedrive docs site, built with Fumadocs on Next.js. This directory is a standalone app with its own bun install, separate from the repo workspace.

bun install
bun run dev      # dev server on localhost:3000
bun run build    # production build

Or from the repo root: just dev-docs / just build-docs. Requires Node 20+.

Layout

overview/, core/, extensions/, cli/, react/, gpui/: published MDX content, one sidebar tab per folder. Navigation order lives in each folder's meta.json.
app/, lib/, components/: the Next.js app. Pages are served from the site root, so core/jobs.mdx renders at /core/jobs.
public/: images, logo, favicon.
plans/, core/design/, design/, archive/: internal working docs, not part of the site.
WRITING_GUIDE.mdx, CODE_COMMENTS.mdx: contributor guides, not published.

Writing pages

Frontmatter supports title, description, and sidebarTitle (a shorter name for the sidebar). Callouts, <Steps>, <Tabs>, <Cards>, and <Accordions> are registered globally, so no imports are needed in MDX. Every page is also served as raw markdown at <path>.md and indexed in /llms.txt.