How ony-boom/mms works
Project type and purpose
• This is a full-stack monorepo called “MMS – My Music Server.”
• Purpose: Provide a web-based local music player. A React client streams and controls audio, while a TypeScript/Nitro server manages the music library, serves files, metadata, and proxies lyrics or cover art.
File structure
• Top-level directories:
• apps/client – React frontend
• apps/server – Nitro/TypeScript backend + Prisma migrations + music-manager library
• packages – shared utilities, config and CLI scripts
• Monorepo orchestrated by Turborepo (turbo.json) and pnpm workspace (pnpm-workspace.yaml).
• Client:
• src/api (GraphQL + REST adapters, wiki)
• src/components, src/hooks, src/context, src/stores, src/pages, src/lib, src/styles
• Bundler: Vite (vite.config.ts)
• Server:
• lib/music-manager (file watcher, track saver)
• prisma (SQLite schema + migrations)
• server/api (route definitions under server/api/…)
• server/plugins (dbInit, musicDirWatcher)
• middleware (CORS)
• Nitro config, tsconfig, .env.example
• packages: share TypeScript and ESLint configs and custom CLI tools.
README insights
• Describes a client-server architecture.
• Tech stack: TypeScript, React, SQLite via Prisma, pnpm, Turborepo, Nix support.
• Emphasis on local music playback, search, playlists (work in progress), modern UI.