AkkalDhami/servercn

Overview Introduce a stateful authentication system using MySQL with Drizzle ORM. This feature provides a scalable and secure authentication mechanism without relying on server-side sessions. Description This feature implements a stateful authentication flow where authentication is handled using tokens while user and related authentication data are persisted in MySQL via Drizzle ORM. The implementation should include proper database schemas, token management, and modular authentication logic that integrates with the existing project architecture. Database Configure MySQL with Drizzle ORM Architecture Support MVC Feature-based(modules) Expected Outcome Fully functional stateful authentication system MySQL database integration using Drizzle ORM Scalable and maintainable authentication architecture Ready-to-use authentication module for the project Reference Stateful Auth (Mongodb) Contributing Guides https://servercn.vercel.app/docs/contributing/blueprint

Overview Introduce a stateless authentication system using PostgreSQL with Drizzle ORM. This feature provides a scalable and secure authentication mechanism without relying on server-side sessions. Description This feature implements a stateless authentication flow where authentication is handled using tokens while user and related authentication data are persisted in PostgreSQL via Drizzle ORM. The implementation should include proper database schemas, token management, and modular authentication logic that integrates with the existing project architecture. Database Configure PostgreSQL with Drizzle ORM Architecture Support MVC Feature-based(modules) Expected Outcome Fully functional stateless authentication system PostgreSQL database integration using Drizzle ORM Scalable and maintainable authentication architecture Ready-to-use authentication module for the project Reference Stateless Auth (MySQL) Contributing Guides https://servercn.vercel.app/docs/contributing/blueprint

Overview Introduce a new prisma-pg-starter foundation that integrates Prisma ORM with PostgreSQL and provides structured starter templates for scalable backend development. Description This foundation should include: Prisma configured for PostgreSQL Base Prisma schema and initial setup Environment configuration Two architecture variants: MVC architecture Feature-based architecture Proper project scaffolding for each variant The objective is to provide a production-ready, minimal, and extensible starting point for Node.js + TypeScript backend applications using Prisma and PostgreSQL. Reference Prisma MongoDB Starterr Requirements The foundation must integrate the following ServerCN components: http-status-codes component health-controller async-handler api-response-formatter global-error-handler logger shutdown-handler Custom ApiError class implementation Starter Template You can start contributing from the Express Starter foundation: https://servercn.vercel.app/docs/express/

Description Add a new nestjs-starter foundation to provide a ready-to-use starter setup for projects using NestJS. Expected Behavior Provide a preconfigured NestJS project structure Include common backend dependencies and best practices Follow the same foundation pattern used by other foundations Allow users to quickly bootstrap a NestJS-based backend Possible Features Basic module/controller/service structure Environment configuration Database integration support (e.g., MongoDB/Prisma) (OPTIONAL) Example route/controller Reference Express Starter Contributing Guides https://servercn.vercel.app/docs/contributing/foundation Motivation Currently, there is no dedicated NestJS foundation. Adding nestjs-starter will allow developers who prefer NestJS to bootstrap projects quickly using ServerCN. Tasks Create nestjs-starter foundation Add CLI option for selecting it Configure basic NestJS project structure Add documentation

Problem Statement Currently, ServerCN components are primarily oriented toward Express-style or generic Node.js patterns. There is no standardized support for: NestJS module-based structure Providers, controllers, and services integration Dependency injection metadata Framework-specific runtime differentiation during build time This limits ServerCN adoption for projects built with NestJS. Proposed NestJS-Compatible Components Introduce production-ready, framework-aware components designed specifically for NestJS: health-ckeck env-config email-service (nodemailer / resend) oauth (google / github / both) file-upload (cloudinary / imagekit) logger (pino / winston) password-hashing (×4) swagger-docs ........more Contributing Guide Contributing Components Guide References ServerCN Components