How logscore/nimbus works
Project type and purpose
• This is a full-stack, monorepo “cloud storage” application called Nimbus cloud storage.
• It provides:
• A browser-based frontend (apps/web) built with Next.js (App Router) and React/TypeScript
• A standalone backend API server (apps/server) in TypeScript (Node/bun)
• Shared packages for authentication (packages/auth) and database access (packages/db)
• It integrates with multiple third-party storage providers (Google Drive, AWS, Azure, GCP, iCloud, OneDrive).
File structure
• Top-level tooling:
• bun.lock, Docker Compose, eslint.config.mjs
• Root package.json and tsconfig.json configure the monorepo workspaces.
• apps/web (Next.js):
• app directory with App Router (pages, api routes for auth)
• components folder with UI primitives, file-browser, upload components
• next.config.ts, postcss.config.mjs, tsconfig.json
• apps/server:
• A small Node/bun server with a Google Drive adapter (lib/google-drive.ts)
• index.ts entry point
• tsconfig.json and package.json
• packages/auth:
• auth.ts (server-side logic) and auth-client.ts (client SDK)
• packages/db:
• Drizzle ORM configuration and migration files
• auth-schema.ts defines user/auth tables
• index.ts export for database client connections
README for additional insights
• Startup instructions use bun i && bun dev to spin up both web and server in development.