How adatechschool/gazette works
Project type and purpose
• This is a full-stack TypeScript monorepo ("gazette") containing:
• A NestJS backend (CommonJS) with MikroORM and PostgreSQL
• A Next.js React frontend
• A shared package for cross-cutting DTOs, enums, interfaces, and schemas
• Its purpose is to serve as a content aggregation platform (“Gazette”) with features like RSS feeds, user authentication, content favoriting, and user settings.
File structure
• Top-level directories:
• apps/backend – NestJS API
• apps/frontend – Next.js web app
• packages/shared – shared DTOs, enums, interfaces, schemas
• Backend follows a modular MVC-style structure:
• src/modules/{auth,content,favorite,rss,user,roles,jwt}
• Entities under src/entities, migrations under src/migrations, MikroORM configs
• Frontend uses Next.js 13 app-folder with route groups for “(auth)” and “(main)”; custom components, providers, services, hooks, contexts, i18n, theme, utils
• Shared package exports strongly-typed DTOs/enums/interfaces for both ends
• Docker files (Dockerfile, docker-compose.yml) define three services: backend, frontend, database
README for additional insights
• Confirms stack: NestJS + MikroORM + Postgres, Next.js
• Shows environment variables, ports, and Docker Compose orchestration
• Mentions migrations, hot-reload considerations, and monorepo layout
Details
• Environment orchestration (Docker Compose) is noted, perhaps as a wrapper around the services.
• Use of MikroORM migrations in the backend.
• Call out SSR vs. API calls in the frontend where useful.
• Authentication flows (e.g., login request → auth module → JWT issuance → protected routes guarded by roles).