TagineStack 🥘

TagineStack is a powerful, opinionated CLI tool for generating production-ready NestJS applications. It streamlines the setup process by providing a modular, plugin-based architecture that lets you choose exactly the features you need.

🌐 Website Application: https://jade-monstera-c26738.netlify.app/

🚀 Features

• Framework: NestJS (Express or Fastify)
• ORMs: Prisma, TypeORM, MikroORM, Sequelize
• Databases: PostgreSQL, MySQL, MongoDB, SQLite
• Authentication:
  • JWT (Local Auth)
  • Keycloak (OIDC)
  • Authentik (OIDC)
• Multi-tenancy:
  • Schema-based (PostgreSQL)
  • Database-based
  • Column-based
• Additional Features:
  • GraphQL (Code-first)
  • Observability (Prometheus/Grafana)
  • i18n (Database or File-based)
  • Linting (ESLint or Biome)
  • Docker Compose setup (Database, Redis, Auth Provider)

📦 Installation

You can use TagineStack directly with npx without installation:

npx tagine-stack

Or install it globally:

npm install -g tagine-stack

🛠 Usage

Simply run the command and follow the interactive prompts:

npx tagine-stack

You will be asked to select:

1. Project Name
2. HTTP Adapter (Express/Fastify)
3. ORM & Database
4. Multi-tenancy Strategy (if needed)
5. Authentication Provider
6. Additional Features (GraphQL, i18n, etc.)

The CLI will generate a complete project structure with all selected configurations, Docker files, and boilerplate code.

🏗 Project Structure

TagineStack generates a dynamic, modular NestJS architecture that adapts to your specific configuration.

Instead of a rigid template, the project structure evolves based on your choices:

• Modular Features: Selected features (Auth, Users, i18n) are generated as self-contained modules.
• Adaptive ORM Setup: Database configurations, entities, and repositories are tailored to your chosen ORM (Prisma, TypeORM, MikroORM, or Sequelize).
• Infrastructure: docker-compose.yml is automatically constructed to include your specific database, Redis (if required), and authentication provider services.
• Clean Architecture: The code is organized with clear separation of concerns, using dedicated directories for configurations, shared utilities, and business logic.