Files
spacedrive/docs
Jamie Pineandcapy-ai-staging[bot] c81e3d6169 Addressing P0 and P1a: doc matches code, content rows record their own bytes (#3112)
* docs: describe addressing as the code does it, mark the target model planned (P0)

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

* store: schema version in PRAGMA user_version, migrated at writer open (P1a)

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

* store: content rows record each file's own bytes (P1a migration 1)

Rebuild content so a row's integrity hash belongs to every record on it:
candidate rows keyed by sampled hash, confirmed rows by integrity hash,
candidate_uuid beside uuid. bind_content never binds a sampled-only write
to a confirmed row, moves need size and mtime, verification claims by
sampled hash, duplicate discovery groups by sampled hash, and content
lookups match uuid or candidate_uuid. Compare-delete matches a file
against any holder in B that was read in full.

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

* store: tests for schema version, migration 1 and content row ownership

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

* status: addressing register row, P0 and P1a landed

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

* store: duplicates group by sampled hash and split by integrity; version-0 tag lookup; content section in the doc

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

* store: bound the duplicates query to the largest group_limit sampled hashes

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

* store: batch migration 1 inserts; timing fixture; upgrade note in the register

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-07 02:57:39 +00:00
..

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.