How do I install the Nestjs Deployment skill?

Run npx skillmds@latest add comeonoliver/nestjs-deployment in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Nestjs Deployment safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Nestjs Deployment?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Nestjs Deployment free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Nestjs Deployment?

ComeOnOliver (@comeonoliver) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Nestjs Deployment by comeonoliver — Agent Skill

Name: Nestjs Deployment
Rating: 4.666666666666667 (3 reviews)
Author: ComeOnOliver

Nestjs Deployment

Docker builds, Memory tuning, and Graceful shutdown. Use when containerizing NestJS apps, tuning memory, or implementing graceful shutdown. (triggers: Dockerfile, k8s/**, helm/**, Dockerfile, max-old-space-size, shutdown hooks)

ComeOnOliver Updated Sep 8, 2026 61 repo stars

File contents

Deployment & Ops Standards

Priority: P1 (OPERATIONAL)

Docker optimization and production deployment standards for NestJS applications.

Docker Optimization

Multi-Stage Builds: Mandatory.
1. Build Stage: Install devDependencies, build NestJS (nest build).
2. Run Stage: Copy only dist and node_modules (pruned), use node:alpine.
Security: Do not run as root.
- Dockerfile: USER node.

Runtime Tuning (Node.js)

Memory Config: Container memory != Node memory.
- Rule: Explicitly set Max Old Space.
- Command: node --max-old-space-size=XXX dist/main
- Calculation: Set to ~75-80% of Kubernetes Limit. (Limit: 1GB -> OldSpace: 800MB).
Graceful Shutdown:
- Signal: Listen to SIGTERM.
- NestJS: app.enableShutdownHooks() is mandatory.
- Sleep: Add a "Pre-Stop" sleep in K8s (5-10s) to allow Load Balancer to drain connections before Node process stops accepting traffic.

Init Patterns

Database Migrations:
- Anti-Pattern: Running migration in main.ts on startup.
- Pro Pattern: Use an Init Container in Kubernetes that runs npm run typeorm:migration:run before the app container starts.

Environment Variables & CI/CD

CI/CD Pipelines (GitHub, GitLab, Azure, etc.):
- If you modify src/config/env.validation.ts to add a new environment variable, you MUST map it explicitly in your deployment pipeline/infrastructure-as-code.
- Platform Context:
  - Cloud Run/ECS: Variables must be explicitly passed in the service definition.
  - Kubernetes: New variables must be added to the Deployment manifest or ConfigMap/Secret.
  - Lambda/Serverless: Must be added to serverless.yml or provider console.
- Fundamental Rule: Application code configuration changes are "breaking changes" for the infrastructure layer. Never assume environment inheritance.

Anti-Patterns

No migrations in main.ts: Use K8s Init Containers or pre-deploy CI steps for migration runs.
No root user in Docker: Always add USER node to Dockerfile; running as root is a security risk.
No unbounded Node heap: Set --max-old-space-size to ~75% of container memory limit.

---name: nestjs-deploymentdescription: Docker builds, Memory tuning, and Graceful shutdown. Use when containerizing NestJS apps, tuning memory, or implementing graceful shutdown. (triggers: Dockerfile, k8s/**, helm/**, Dockerfile, max-old-space-size, shutdown hooks)---# Deployment & Ops Standards## **Priority: P1 (OPERATIONAL)**Docker optimization and production deployment standards for NestJS applications.## Docker Optimization- **Multi-Stage Builds**: Mandatory. 1. **Build Stage**: Install `devDependencies`, build NestJS (`nest build`). 2. **Run Stage**: Copy only `dist` and `node_modules` (pruned), use `node:alpine`.- **Security**: Do not run as `root`. - **Dockerfile**: `USER node`.## Runtime Tuning (Node.js)- **Memory Config**: Container memory != Node memory. - **Rule**: Explicitly set Max Old Space. - **Command**: `node --max-old-space-size=XXX dist/main` - **Calculation**: Set to ~75-80% of Kubernetes Limit. (Limit: 1GB -> OldSpace: 800MB).- **Graceful Shutdown**: - **Signal**: Listen to `SIGTERM`. - **NestJS**: `app.enableShutdownHooks()` is mandatory. - **Sleep**: Add a "Pre-Stop" sleep in K8s (5-10s) to allow Load Balancer to drain connections before Node process stops accepting traffic.## Init Patterns- **Database Migrations**: - **Anti-Pattern**: Running migration in `main.ts` on startup. - **Pro Pattern**: Use an **Init Container** in Kubernetes that runs `npm run typeorm:migration:run` before the app container starts.## Environment Variables & CI/CD- **CI/CD Pipelines (GitHub, GitLab, Azure, etc.)**: - If you modify `src/config/env.validation.ts` to add a new environment variable, you **MUST** map it explicitly in your deployment pipeline/infrastructure-as-code. - **Platform Context**: - **Cloud Run/ECS**: Variables must be explicitly passed in the service definition. - **Kubernetes**: New variables must be added to the `Deployment` manifest or `ConfigMap`/`Secret`. - **Lambda/Serverless**: Must be added to `serverless.yml` or provider console. - **Fundamental Rule**: Application code configuration changes are "breaking changes" for the infrastructure layer. Never assume environment inheritance.## Anti-Patterns- **No migrations in main.ts**: Use K8s Init Containers or pre-deploy CI steps for migration runs.- **No root user in Docker**: Always add `USER node` to Dockerfile; running as root is a security risk.- **No unbounded Node heap**: Set `--max-old-space-size` to ~75% of container memory limit.

Frequently asked questions