How whyleonardo/dropcode works
Project Type and Purpose
• Dropcode is a monorepo-managed code-snippet manager.
• It hosts two frontends:
– apps/marketing (Astro-built static marketing site)
– apps/web (Next.js full-stack application for snippet management)
• Shared libraries/packages provide auth, DB, Redis, env, and config.
File Structure
• Top-level:
– apps/marketing – static site
– apps/web – React/Next.js app with API routes & server actions
– packages/* – reusable modules (auth, db, redis, env)
– config/* – custom Tailwind, asset, and TS config
– turbo.json – Turborepo build orchestration
– docker-compose.yml – local container setup
• apps/web contains:
– src/app/api (Next.js serverless routes using Auth.js)
– src/data (Zod schemas + server-side data functions)
– src/components, src/lib, src/hooks, src/providers (client + SSR)
• Packages:
– packages/db wraps Prisma → PostgreSQL
– packages/redis exports Redis client
– packages/auth configures Auth.js providers
– packages/env centralizes environment variables
README for Additional Insights
• Tech stack: Next.js, Astro, Turborepo, Docker, Prisma, Redis, Postgres, Auth.js, TypeScript, Tailwind, React Query, Zod, Framer Motion, etc.
• Features: snippet/file CRUD, analytics, authentication, caching, schema validation.
Components & Relationships
a. Main Components
– Frontends
• Marketing Site (Astro static pages)
• Web App (Next.js + React client + serverless API)
– Shared Packages (auth, db, redis, env)
– Build System (Turborepo)
– Database (PostgreSQL via Prisma)
– Cache (Redis)
– External Services (Auth providers via Auth.js, e.g., GitHub)
– DevOps (Docker Compose)
b. Interactions & Data Flows
– User → Browser → Marketing Site (static pages)
– User → Browser → Web App Client
– Web App Client → Next.js Server (API Routes / Server Actions)
– Next.js Server ↔ packages/auth (Auth.js config) for login/session
– Next.js Server ↔ packages/db (Prisma) → Postgres
– Next.js Server ↔ packages/redis → Redis (caching, sessions)
– Build System orchestrates dep graph: apps ← packages ← config
– Docker Compose spins up Postgres & Redis locally
c. Architectural Patterns & Design Principles
– Monorepo with Turborepo for parallel builds & caching
– Package-driven modularization (auth, db, redis, env)
– Next.js App Router + Server Actions (ZSA)
– Zod for runtime schema validation
– React Query / TanStack Query for data fetching & caching
– Tailwind CSS + Shadcn/Radix UI for styling
d. Key Technologies to Call Out
– Next.js (SSR, SSG, Server Actions)
– Astro (static marketing site)
– Prisma ORM → PostgreSQL
– Redis (in-memory cache)
– Auth.js (OAuth flows)
– Turborepo (monorepo orchestration)
– Docker Compose (local services)