Starter template for 😻 NestJS and Prisma.
Checkout NestJS Prisma Schematics to automatically add Prisma support to your Nest application.
- Prisma for database modelling, migration and type-safe access (Postgres, MySQL & MongoDB)
- 🔐 JWT authentication w/ passport-jwt
- REST API docs w/ Swagger
Install Nestjs CLI to start and generate CRUD resources
npm i -g @nestjs/cli
Install the dependencies for the Nest application:
npm install
Setup a development PostgreSQL with Docker. Copy .env.example and rename to .env
- cp .env.example .env
- which sets the required environments for PostgreSQL such as POSTGRES_USER
, POSTGRES_PASSWORD
and POSTGRES_DB
. Update the variables as you wish and select a strong password.
Start the PostgreSQL database
docker-compose -f docker-compose.db.yml up -d
# or
npm run docker:db
Prisma Migrate is used to manage the schema and migration of the database. Prisma datasource requires an environment variable DATABASE_URL
for the connection to the PostgreSQL database. Prisma reads the DATABASE_URL
from the root .env file.
Use Prisma Migrate in your development environment to
- Creates
migration.sql
file - Updates Database Schema
- Generates Prisma Client
npx prisma migrate dev
# or
npm run migrate:dev
If you like to customize your migration.sql
file run the following command. After making your customizations run npx prisma migrate dev
to apply it.
npx prisma migrate dev --create-only
# or
npm run migrate:dev:create
If you are happy with your database changes you want to deploy those changes to your production database. Use prisma migrate deploy
to apply all pending migrations, can also be used in CI/CD pipelines as it works without prompts.
npx prisma migrate deploy
# or
npm run migrate:deploy
Prisma Client JS is a type-safe database client auto-generated based on the data model.
Generate Prisma Client JS by running
Note: Every time you update schema.prisma re-generate Prisma Client JS
npx prisma generate
# or
npm run prisma:generate
Execute the script with this command:
npm run seed
Run Nest Server in Development mode:
npm run start
# watch mode
npm run start:dev
Run Nest Server in Production mode:
npm run start:prod
RESTful API documentation available with Swagger.
Nest server is a Node.js application and it is easily dockerized.
See the Dockerfile on how to build a Docker image of your Nest server.
Now to build a Docker image of your own Nest server simply run:
# give your docker image a name
docker build -t <your username>/nest-prisma-server .
# for example
docker build -t nest-prisma-server .
After Docker build your docker image you are ready to start up a docker container running the nest server:
docker run -d -t -p 3000:3000 --env-file .env nest-prisma-server
Now open up localhost:3000 to verify that your nest server is running.
When you run your NestJS application in a Docker container update your .env file
- DB_HOST=localhost
# replace with name of the database container
+ DB_HOST=postgres
# Prisma database connection
+ DATABASE_URL=postgresql://${POSTGRES_USER}:${POSTGRES_PASSWORD}@${DB_HOST}:${DB_PORT}/${POSTGRES_DB}?schema=${DB_SCHEMA}&sslmode=prefer
If DATABASE_URL
is missing in the root .env
file, which is loaded into the Docker container, the NestJS application will exit with the following error:
(node:19) UnhandledPromiseRejectionWarning: Error: error: Environment variable not found: DATABASE_URL.
--> schema.prisma:3
|
2 | provider = "postgresql"
3 | url = env("DATABASE_URL")
You can also setup a the database and Nest application with the docker-compose
# building new NestJS docker image
docker-compose build
# or
npm run docker:build
# start docker-compose
docker-compose up -d
# or
npm run docker
Update the Prisma schema prisma/schema.prisma
and after that run the following two commands:
npx prisma generate
# or in watch mode
npx prisma generate --watch
# or
npm run prisma:generate
npm run prisma:generate:watch
To authenticate your requests you have to add your TOKEN
you receive on signup
and login
mutation to each request which is protected by the @UseGuards(GqlAuthGuard)
.
Because the apollo client is using HttpClient
under the hood you are able to simply use an Interceptor
to add your token to the requests.
Create the following class:
import { Injectable } from '@angular/core';
import {
HttpEvent,
HttpInterceptor,
HttpHandler,
HttpRequest,
} from '@angular/common/http';
import { Observable } from 'rxjs';
@Injectable()
export class TokenInterceptor implements HttpInterceptor {
constructor() {}
intercept(
req: HttpRequest<any>,
next: HttpHandler
): Observable<HttpEvent<any>> {
const token = 'YOUR_TOKEN'; // get from local storage
if (token !== undefined) {
req = req.clone({
setHeaders: {
Authorization: `Bearer ${token}`,
},
});
}
return next.handle(req);
}
}
Add the Interceptor to the AppModule
providers like this:
providers: [
...
{ provide: HTTP_INTERCEPTORS, useClass: TokenInterceptor, multi: true },
...
]
After you configured the Interceptor and retrieved the TOKEN
from storage your request will succeed on resolvers with @UseGuards(GqlAuthGuard)
.
- get by id returns 200 even if entity not found
- deleting entity that does not exists returns 500
- select enum values from dropdown