How dipesh1203/scribble_hub works
Project type and purpose
• This is a Turborepo-based full-stack real-time collaborative drawing and chat application.
• It contains three “apps” in the monorepo:
• scribbledraw-frontend (Next.js + React + Konva for canvas + NextAuth)
• http-backend (Node.js/TypeScript REST API for auth, rooms, chat)
• ws-backend (Node.js/TypeScript WebSocket server for realtime drawing events)
• Shared packages:
• packages/common (shared types, server.address constants)
• packages/db (Prisma schema + migrations, DB access)
• packages/ui (shared React component library)
• packages/eslint-config & packages/typescript-config for toolchain config
File structure
• Top-level “apps” directory holds three independently runnable services.
• “packages” directory holds internal libraries and configuration.
• Root contains PNPM/Turbo configs, Docker compose files, GitHub Actions workflows for CI/CD.
• Apps reference shared packages via workspace imports (e.g. @repo/common, @repo/db, @repo/ui).
README for additional insights
• Confirms a Turborepo monorepo with multiple apps & shared packages.
• Mentions TypeScript, ESLint, Prettier, remote caching – but does not detail the drawn app itself.
Detail
• NextAuth endpoints in frontend under API layer.
• Dockerfiles and GitHub Actions per service for a deployment-centric view.