Drive

Overview

Drive (ZNL-DRIVE) is a SvelteKit file workspace that feels like a familiar cloud drive while staying under your control. Metadata — hierarchy, labels, pin/star, trash, shares, and storage provider — lives in Postgres via Drizzle. Bytes live on either the server filesystem (Local) or Tigris S3-compatible object storage. The same product exposes a browser UI, cookie sessions, and developer API keys for automation.

Problem it solves

Most “drive” demos hard-code one bucket and skip team spaces, trash retention, or a public API. Drive treats storage as a product surface: switch providers without rewriting the UI, share with signed-in users or anonymous link tokens, and operate teams with their own storage target. Deployments run on Docker or Fly.io with Neon Postgres.

Home library

Home is the primary library. Breadcrumbs track folder depth; row actions cover rename, color labels, pin, star, download, share, public link, and move to trash. The NEW menu creates folders, uploads files, and can create a team. There is no global top-bar search — navigation is intentional through Home, Shared, Teams, Recent, Trash, and Dashboard.

Storage providers

A navbar selector chooses the active target for new uploads and folders. Existing rows keep the provider they were written with. Team drives lock to the team’s configured provider so members do not accidentally split a shared space across backends.

• Local — server filesystem under a mounted data directory (ideal for LAN / single-node Docker)
• Tigris — S3-compatible object storage via the Tigris SDK
• Architecture leaves room for other S3-compatible backends (R2, MinIO, B2, etc.)

Upload & download

Small files upload as binary application/octet-stream; larger files use chunked upload sessions (≈8 MiB chunks) assembled on disk before finalize. MIME is inferred from filenames when the browser sends an empty type. Downloads stream a single file or a ZIP for folders. Upload/create actions are disabled in Shared and Trash with clear UI copy.

Sharing & collaboration

1. 01 User share — grant another account access; Shared view is read-oriented (browse/download, no upload into someone else’s tree)
2. 02 Team drives — shared spaces under Teams; create from NEW, invite members, list membership via /api/teams
3. 03 Public links — revocable random tokens; human share page at /{token} plus direct /api/public/files/{token} for raw bytes or folder ZIP; images preview inline, other types download
4. 04 Docs under /onboarding/docs never collide with share tokens (fixed path prefix)

Trash & retention

Items leave Home when trashed and appear in the Trash sidebar view for restore or permanent delete. A cron endpoint (Bearer CRON_SECRET) purges expired trash on a schedule so operators can enforce retention policy without manual cleanup.

Auth & developer mode

Better Auth powers email/password plus optional GitHub and Google OAuth. Drive JSON/binary APIs accept a session cookie or a developer API key (Authorization / X-API-Key). Key CRUD and developer-mode toggles require a cookie session so keys cannot manage themselves. Settings expose profile, storage preferences, and logout.

REST surface (highlights)

1. 01 GET/POST /api/drive/files & folders — list, create, patch pin/star/name/color/trash
2. 02 POST /api/drive/upload (+ /chunk) — binary and chunked uploads
3. 03 GET …/download, …/public-link; POST/DELETE public-link and share
4. 04 GET /api/drive/shared, /trash, /stats
5. 05 GET/POST /api/teams — membership and team creation
6. 06 GET /api/public/share/{token} and /api/public/files/{token} — anonymous access
7. 07 Developer mode + API key CRUD under /api/developer/*

Architecture

Requests enter SvelteKit routes, resolve auth (cookie or API key), then hit small server handlers that query Postgres for metadata and open Local or Tigris blobs for bytes. Public link tokens are a separate table so anonymous traffic never needs a session. Onboarding docs are mdsvex routes with a drawer sidebar — prerender-safe because they do not read private data.

Stack & ops

1. 01 SvelteKit 2 + Svelte 5, Tailwind CSS 4, daisyUI 5 (prefixed d- classes)
2. 02 Postgres (Neon) + Drizzle ORM; Better Auth sessions
3. 03 Deno 2 task runner for install/dev/db scripts; Node for Vite build and production runtime
4. 04 Docker volume for Local data; BODY_SIZE_LIMIT per chunk; ORIGIN-sensitive CSRF/cookie Secure behavior
5. 05 Paraglide i18n; Playwright + unit tests; GPLv3

Design decisions

1. 01 Metadata in SQL, blobs in pluggable storage — so listing, trash, and shares stay fast regardless of backend
2. 02 Chunked uploads with on-disk assembly — large media without loading whole files into memory
3. 03 API keys as first-class auth — scripts and agents can use the same drive APIs as the UI
4. 04 Team storage affinity — one shared space maps to one provider, avoiding split-brain folders