This is a NestJS boilerplate for building RESTful APIs with TypeScript, PostgreSQL, TypeORM, and modern DevOps practices. The system provides a modular backend architecture with authentication (JWT), user management, post management, email verification via BullMQ queues, health checks, Swagger API documentation, and comprehensive testing setup. It follows NestJS best practices with clear separation of concerns across modules for auth, users, posts, health, and background jobs. Key features include cursor-based and offset-based pagination, internationalization (i18n), Redis caching, security headers via Helmet, and environment-based configuration management. The codebase demonstrates strong engineering practices with reusable utilities for password handling, configuration validation, and sophisticated cursor pagination that could be extracted to other projects with minimal modification.
This repository is the source code for the NG-NEST Angular UI component library (version 22.0.5), providing over 70 reusable components for building enterprise-grade web applications. The library includes a comprehensive set of UI elements such as buttons, tables, forms, dialogs, trees, date pickers, and more, all built with Angular's latest features including signals, standalone components, and OnPush change detection. The repository also contains a documentation/demo site that showcases each component with live examples in both English and Chinese, along with a full RBAC tutorial demonstrating a real-world admin panel using NestJS and Angular. The architecture follows a monorepo pattern: the library lives under `lib/ng-nest/ui/` with each component as an independent Angular module (with its own `ng-package.json`), while the documentation site resides in `src/` and uses the library itself. Key entry points include `lib/ng-nest/ui/index.ts` for the library and `src/app/app.config.ts` for the application. Data flows are primarily unidirectional via Angular signals and observables, with services like `XRepositoryAbstract` providing a consistent CRUD pattern for backend integration. External dependencies include Angular 22, Angular CDK, RxJS, and PrismJS for syntax highlighting. The library demonstrates strong engineering practices: consistent component property classes, a centralized portal service for overlays, a theme system with CSS variables and dark mode, and full internationalization support with 30+ locales. However, many component tests are disabled (using `xdescribe`), and there is some duplication in example data across language variants. Overall, it is a well-maintained, production-ready UI library with a high degree of reusability.
Runtipi is a self-hosted homeserver orchestrator: a web-based control plane for installing, updating, backing up, and managing Docker Compose applications on a single server. In production it runs as a NestJS backend, a React frontend, and a shared TypeScript schema package, with PostgreSQL as the primary datastore, RabbitMQ for asynchronous job queues, Dockerode for container control, and Traefik as the reverse proxy and TLS/forward-auth gateway. The app-store model clones external git repositories containing app manifests and compose definitions, then validates and renders them through a dynamic form system. The architecture is a monolithic backend organized around modules for app lifecycle, marketplace, app stores, backups, auth, links, settings, and i18n; long-running operations are executed through a command/handler pattern with per-app async mutexes and schema-validated RabbitMQ event queues.
This repository implements a RESTful API for a simple todo application with user authentication, built using NestJS, Passport, TypeORM, and PostgreSQL. It provides registration and login (local strategy with JWT), session management via cookies, and CRUD operations for todos and user profiles. The architecture is a monolithic NestJS application with clearly separated modules (Auth, Todo, User) and uses standard patterns such as guards, interceptors, pipes, and filters. The codebase is well-tested with unit and end-to-end tests, includes stress testing with k6, and follows modern TypeScript practices with decorators and dependency injection. It serves as a practical example of integrating Passport authentication (local and JWT strategies) with NestJS and TypeORM, including custom validators, pagination interceptors, and ownership checks.
This repository contains the official documentation website for the Remnawave proxy management panel. Built with Docusaurus 3.9.x and React 19, it generates a static site that provides installation guides, configuration references, tutorials, and API documentation. The site features a landing page with custom React components (hero section, stats bar, feature highlights, project grids, client cards) and multilingual help articles covering authentication methods, editor templates, and page configurations. A Caddy server serves the built output with routing for the landing page and documentation paths. The repository also includes an awesome-remnawave page indexing community tools (backup scripts, bots, monitoring tools) and a curated list of proxy clients with data-driven card displays. While the actual Remnawave panel backend is hosted separately, this documentation site is a well-structured, actively maintained resource that follows Docusaurus best practices with custom theming, dark mode, and analytics integration.
The repository is a full-stack application template providing role-based access control (RBAC) with a modern frontend and multiple backend options. It features a React/Vite frontend built with Shadcn UI and Tailwind CSS, offering comprehensive UI components, dashboards, and charting capabilities. Two backend implementations are provided: Spring Boot (Java) and NestJS (TypeScript), both featuring JWT authentication, PostgreSQL integration, and CRUD operations for users, roles, permissions, and groups. The frontend showcases a well-crafted component library including reusable UI primitives, custom extensions like tree selectors and context menus, and themed chart containers. State management is handled via Zustand, with internationalization via react-intl and API mocking using MSW. The backends follow standard layered architectures with service-repository patterns, DTO validation, and security configurations. While the Spring Boot backend contains a non-standard Java 25 version specification (likely a typo) posing build risks, the NestJS backend uses current LTS Node.js versions. The project demonstrates solid full-stack engineering with modular design, clear separation of concerns, and reusable UI patterns. Despite the Java version concern in one backend, the template remains a valuable foundation for enterprise admin panels with modern tooling.
WeWe RSS is a monolithic NestJS application that provides RSS feed generation for WeChat public accounts (ĺžŽäżĄĺ Źäźĺˇ). It acts as a middleware between the WeRead (垎俥话䚌) platform and standard RSS readers. The system allows users to add WeChat public accounts via article links, fetches account metadata and article lists through the WeRead platform API, stores them in a MySQL or SQLite database, and exposes RSS/Atom/JSON feeds. It includes a cron-based scheduler for periodic feed updates, an admin dashboard built with React and NextUI, and supports features like full-text extraction, title filtering, and OPML export. The architecture is typical for a NestJS application: controllers handle HTTP requests, tRPC provides a type-safe API layer for the frontend, Prisma ORM manages database interactions, and the frontend is a separate Vite/React app. The codebase is straightforward and functional, with no standout reusable components that could be easily extracted without modification.
Pingvin Share is a self-hosted file sharing platform designed as an alternative to services like WeTransfer. It provides a full-stack application with a NestJS backend and a Next.js frontend, featuring user authentication (local, OAuth2, TOTP, LDAP), file uploads with chunked transfers, password-protected and expiring shares, reverse shares for receiving files, an administrative panel for managing users and system configuration, and support for multiple storage backends (local filesystem or S3). The application includes virus scanning via ClamAV, email notifications, and extensive internationalization. The backend employs a modular architecture with distinct modules for authentication, user management, share handling, file storage, configuration, and scheduled jobs. Key reusable patterns include an abstracted file storage service (supporting local and S3 providers), a strategy-based OAuth provider interface, and a dynamic configuration service that loads settings from the database with optional YAML file overrides and runtime update notifications. The frontend presents a polished user interface with custom hooks for configuration and user state, reusable input components for timespans and file sizes, and a sophisticated chunked file upload UI with progress tracking and error recovery. Although the original repository has been archived (as of June 2025) with a recommendation to use a maintained fork, the codebase demonstrates solid engineering practices, clear separation of concerns, and several reusable components that could be adapted for similar projects. The Dockerized deployment and comprehensive feature set make it a viable self-hosted solution for file sharing needs.