zenhosta/9drive

Purpose and Entry Points

9Drive is a virtual storage gateway that unifies users’ Google Drive accounts and S3-compatible providers behind a React dashboard and external upload API. The backend is an Express/TypeScript service booted by backend/src/server.ts, composed in backend/src/app.ts; the browser client starts at frontend/src/main.tsx and routes from frontend/src/App.tsx.

API Boundary and Authorization

HTTP routes are organized by domain modules and protected with bearer-JWT authentication or API-key middleware. Authentication includes local credentials, Google OAuth, refresh/logout flows, and OAuth handoff; app/session secrets and provider credentials are encrypted or hashed.

• backend/src/modules/auth/auth.routes.ts

• backend/src/middleware/auth.middleware.ts

• backend/src/middleware/api-key.middleware.ts

Persistent Control Plane

MySQL, accessed through Prisma, is the system of record for users, sessions, connected providers, virtual folder hierarchy, file metadata, share/preview tokens, routing policies, API keys, and audit history. Prisma migrations define the evolving persistence contract, including S3 providers and resumable upload fields.

• backend/prisma/schema.prisma

• backend/src/config/prisma.ts

• backend/prisma/migrations/20260611120000_s3_storage_support/migration.sql

Provider Integration Layer

Google Drive is both an OAuth identity source and storage backend: credentials are stored as encrypted global/provider configuration, connected accounts are managed per user, and Drive contents are synchronized into MySQL metadata. S3-compatible storage is accessed server-side so browser clients never receive storage credentials.

• backend/src/modules/google/google.service.ts

• backend/src/modules/s3/s3.service.ts

• backend/src/modules/connected-accounts/connected-account.routes.ts

Upload Routing and File Lifecycle

Uploads enter through authenticated UI uploads or /api/v1/uploads API-key uploads. The backend streams bytes directly to the selected Google Drive or S3 provider rather than retaining files locally. Routing policies choose a target account/provider by available capacity, round-robin, or priority. File operations then cover listing/search, virtual-folder assignment, rename/move/delete, share links, preview tokens, downloads, and provider streaming.

• backend/src/modules/uploads/upload.routes.ts

• backend/src/modules/files/file.routes.ts

• backend/src/modules/files/stream-google-file.ts

Frontend Workspace

The Vite React single-page application provides protected dashboard pages for files, sharing, quota, activity, provider setup, OAuth completion, and API-key management. A shared API/auth client bridges it to Express; upload state is centralized so progress can persist across dashboard views.

• frontend/src/layouts/DriveLayout.tsx

• frontend/src/lib/api.ts

• frontend/src/context/UploadContext.tsx

Deployment and External Dependencies

Runtime dependencies are Node.js 20+, MySQL 8+, Google OAuth/Drive API, and optionally any S3-compatible endpoint (AWS S3, MinIO, R2, etc.). Docker Compose provisions frontend, backend, and MySQL; the backend applies Prisma migrations and can seed Google configuration at startup. Production frontend is served through Nginx.

• docker-compose.yml

• backend/Dockerfile

• frontend/nginx.conf