API with NestJS #2. Setting up a PostgreSQL database with TypeORM

May 18, 2020

The next important thing when learning how to create an API is how to store the data. In this article, we look into how to do so with PostgreSQL and NestJS. To make the managing of a database more convenient, we use an Object-relational mapping (ORM) tool called TypeORM. To have an even better understanding, we also look into some SQL queries. By doing so, we can grasp what advantages ORM gives us.

You can find all of the below code in this repository.

Creating a PostgreSQL database

The most straightforward way of kickstarting our development with a Postgres database is to use docker.
Here, we use the same setup as in the TypesScript Express series.

The first thing to do is to install Docker and Docker Compose. Now, we need to create a docker-compose file and run it.

docker-compose.yml

version: "3"

services:

postgres:

container_name: postgres

image: postgres:latest

ports:

- "5432:5432"

volumes:

- /data/postgres:/data/postgres

env_file:

- docker.env

networks:

- postgres

pgadmin:

links:

- postgres:postgres

container_name: pgadmin

image: dpage/pgadmin4

ports:

- "8080:80"

volumes:

- /data/pgadmin:/root/.pgadmin

env_file:

- docker.env

networks:

- postgres

networks:

postgres:

driver: bridge

The useful thing about the above configuration is that it also starts a pgAdmin console. It gives us the possibility to view the state of our database and interact with it.

To provide credentials used by our Docker containers, we need to create the docker.env file. You might want to skip committing it by adding it to your .gitignore.

docker.env

POSTGRES_USER=admin

POSTGRES_PASSWORD=admin

POSTGRES_DB=nestjs

PGADMIN_DEFAULT_EMAIL=admin@admin.com

PGADMIN_DEFAULT_PASSWORD=admin

Once all of the above is set up, we need to start the containers:

1	docker-compose up

Environment variables

A crucial thing to running our application is to set up environment variables. By using them to hold configuration data, we can make it easily configurable. Also, it is easier to keep sensitive data from being committed to a repository.

In the Express Typescript series, we use a library called dotenv to inject our variables. In NestJS, we have a ConfigModule that we can use in our application. It uses dotenv under the hood.

1	npm install @nestjs/config

app.module.ts

import { Module } from '@nestjs/common';

import { PostsModule } from './posts/posts.module';

import { ConfigModule } from '@nestjs/config';

@Module({

imports: [PostsModule, ConfigModule.forRoot()],

controllers: [],

providers: [],

})

export class AppModule {}

As soon as we create a .env file at the root of our application, NestJS injects them into a ConfigSerivice that we will use soon.

.env

POSTGRES_HOST=localhost

POSTGRES_PORT=5432

POSTGRES_USER=admin

POSTGRES_PASSWORD=admin

POSTGRES_DB=nestjs

PORT=5000

Validating environment variables

It is an excellent idea to verify our environment variables before running the application. In the TypeScript Express series, we’ve used a library called envalid.

The ConfigModule built into NestJS supports @hapi/joi that we can use to define a validation schema.

1	npm install @hapi/joi @types/hapi__joi

app.module.ts

import { Module } from '@nestjs/common';

import { PostsModule } from './posts/posts.module';

import { ConfigModule } from '@nestjs/config';

import * as Joi from '@hapi/joi';

@Module({

imports: [

PostsModule,

ConfigModule.forRoot({

validationSchema: Joi.object({

POSTGRES_HOST: Joi.string().required(),

POSTGRES_PORT: Joi.number().required(),

POSTGRES_USER: Joi.string().required(),

POSTGRES_PASSWORD: Joi.string().required(),

POSTGRES_DB: Joi.string().required(),

PORT: Joi.number(),

})

controllers: [],

providers: [],

})

export class AppModule {}

Connecting a NestJS application with PostgreSQL

A first thing to do once we have our database running is to define a connection between our application and the database. To do so, we use TypeOrmModule.

1	npm install @nestjs/typeorm typeorm pg

To keep our code clean, I suggest creating a database module.

database.module.ts

import { Module } from '@nestjs/common';

import { TypeOrmModule } from '@nestjs/typeorm';

import { ConfigModule, ConfigService } from '@nestjs/config';

@Module({

imports: [

TypeOrmModule.forRootAsync({

imports: [ConfigModule],

inject: [ConfigService],

useFactory: (configService: ConfigService) => ({

type: 'postgres',

host: configService.get('POSTGRES_HOST'),

port: configService.get('POSTGRES_PORT'),

username: configService.get('POSTGRES_USER'),

password: configService.get('POSTGRES_PASSWORD'),

database: configService.get('POSTGRES_DB'),

entities: [

__dirname + '/../**/*.entity.ts',

synchronize: true,

})

}),

})

export class DatabaseModule {}

The synchronize flag above is very important. We will elaborate on it a lot later

An essential thing above is that we use the ConfigModule and ConfigService. The useFactory method can access the environment variables thanks to providing the imports and inject arrays. We elaborate on these mechanisms in the upcoming parts of this series.

Now, we need to import our DatabaseModule.

app.module.ts

import { Module } from '@nestjs/common';

import { PostsModule } from './posts/posts.module';

import { ConfigModule } from '@nestjs/config';

import * as Joi from '@hapi/joi';

import { DatabaseModule } from './database/database.module';

@Module({

imports: [

PostsModule,

ConfigModule.forRoot({

validationSchema: Joi.object({

POSTGRES_HOST: Joi.string().required(),

POSTGRES_PORT: Joi.number().required(),

POSTGRES_USER: Joi.string().required(),

POSTGRES_PASSWORD: Joi.string().required(),

POSTGRES_DB: Joi.string().required(),

PORT: Joi.number(),

})

}),

DatabaseModule,

controllers: [],

providers: [],

})

export class AppModule {}

Entities

The most crucial concept to grasp when using TypeORM is the entity. It is a class that maps to a database table. To create it, we use the @Entity() decorator.

post.entity.ts

import { Column, Entity, PrimaryGeneratedColumn } from 'typeorm';

@Entity()

class Post {

@PrimaryGeneratedColumn()

public id: number;

@Column()

public title: string;

@Column()

public content: string;

}

export default Post;

A neat thing about TypeORM is that it integrates well with TypeScript because it is written in it. To define our columns, we can use various decorators.

@PrimaryGeneratedColumn()

A primary key is a column used to identify a row uniquely in a table. Although we might use an existing column and make it primary, we usually create an id column. By choosing PrimaryGeneratedColumn from TypeORM, we create an integer primary column that has a value generated automatically.

@Column()

The @Column() decorator marks a property as a column. When using it, we have two possible approaches.

The first approach is not to pass the column type explicitly. When we do it, TypeORM figures out the column using our TypeScript types. It is possible because NestJS uses reflect-metadata under the hood.

The second approach would be to pass the type of column explicitly, for example, by using @Column('text'). The available column types differ between databases like MySQL and Postgres. You can look them up in the TypeORM documentation.

It is a proper moment to discuss different ways to store strings in Postgres. Relying on TypeORM to figure out the type of a string column results in the “character varying” type, also called varchar.

Varchar is very similar to a text type of a column but gives us a possibility to limit the length of a string. Both types are the same performance-wise.

SQL query

In pgAdmin, we can check a query equivalent to what TypeORM did for us under the hood.

CREATE TABLE public.post

(

id integer NOT NULL DEFAULT nextval('post_id_seq'::regclass),

title character varying COLLATE pg_catalog."default" NOT NULL,

content character varying COLLATE pg_catalog."default" NOT NULL,

CONSTRAINT "PK_be5fda3aac270b134ff9c21cdee" PRIMARY KEY (id)

)

There are a few interesting things to notice above

Using @PrimaryGeneratedColumn() results in having an int column. It defaults to the return value of a nextval function that returns unique ids. An alternative would be to use a serial type instead and would make the query shorter, but it works the same under the hood.

Our entity has varchar columns that use COLLATE. Collation is used to specify the sort order and character classification. To see our default collation, we can run this query:

1	SHOW LC_COLLATE

en_US.utf8

The above value is defined in a query that was used to create our database. It is UTF8 and English by default.

CREATE DATABASE nestjs

WITH

OWNER = admin

ENCODING = 'UTF8'

LC_COLLATE = 'en_US.utf8'

LC_CTYPE = 'en_US.utf8'

TABLESPACE = pg_default

CONNECTION LIMIT = -1;

Also, our CREATE TABLE query puts a constraint on our ids so that they are always unique.

PK_be5fda3aac270b134ff9c21cdee is a name of the above constraint and was generated

Repositories

With repositories, we can manage a particular entity. A repository has multiple functions to interact with entities. To access it, we use the TypeOrmModule again.

posts.module.ts

import { Module } from '@nestjs/common';

import PostsController from './posts.controller';

import PostsService from './posts.service';

import Post from './post.entity';

import { TypeOrmModule } from '@nestjs/typeorm';

@Module({

imports: [TypeOrmModule.forFeature([Post])],

controllers: [PostsController],

providers: [PostsService],

})

export class PostsModule {}

Now, in our PostsService, we can inject the Posts repository.

1	import { InjectRepository } from '@nestjs/typeorm';

constructor(

@InjectRepository(Post)

private postsRepository: Repository<PostEntity>

) {}

Finding

With the find function, we can get multiple elements. If we don’t provide ith with any options, it returns all.

getAllPosts() {

return this.postsRepository.find();

}

To get just one element we use the findOne function. By providing it with a number we indicate that we want an element with a particular id. If the result is undefined, it means that the element wasn’t found.

async getPostById(id: number) {

const post = await this.postsRepository.findOne(id);

if (post) {

return post;

}

throw new HttpException('Post not found', HttpStatus.NOT_FOUND);

}

Creating

By using the create function, we can instantiate a new Post. We can use the save function afterward to populate the database with our new entity.

async createPost(post: CreatePostDto) {

const newPost = await this.postsRepository.create(post);

await this.postsRepository.save(newPost);

return newPost;

}

Modifying

To modify an existing element, we can use the update function. Afterward, we would use the findOne function to return the modified element.

async updatePost(id: number, post: UpdatePostDto) {

await this.postsRepository.update(id, post);

const updatedPost = await this.postsRepository.findOne(id);

if (updatedPost) {

return updatedPost

}

throw new HttpException('Post not found', HttpStatus.NOT_FOUND);

}

A significant thing is that it accepts a partial entity, so it acts as a PATCH, not as a PUT. If you want to read more on PUT vs PATCH (although with MongoDB), check out TypeScript Express tutorial #15. Using PUT vs PATCH in MongoDB with Mongoose

Deleting

To delete an element with a given id, we can use the delete function.

async deletePost(id: number) {

const deleteResponse = await this.postsRepository.delete(id);

if (!deleteResponse.affected) {

throw new HttpException('Post not found', HttpStatus.NOT_FOUND);

}

By checking out the documentation of the DELETE command, we can see that we have access to the count of removed elements. This data is available in the affected property. If it equals zero, we can assume that the element does not exist.

Handling asynchronous errors

A beneficial thing about NestJS controllers is that they handle asynchronous errors very well.

@Get(':id')

getPostById(@Param('id') id: string) {

return this.postsService.getPostById(Number(id));

}

If the getPostById function throws an error, NestJS catches it automatically and parses it. When using pure Express, we would do this ourselves:

getAllPosts = async (request: Request, response: Response, next: Next) => {

const id = request.params.id;

try {

const post = await this.postsService.getPostById();

response.send(post);

} catch (error) {

next(error);

}

Summary

In this article, we’ve gone through the basics of connecting our NestJS application with a PostgreSQL database. Not only did we use TypeORM, but we’ve also looked into some SQL queries. NestJS and TypeORM have lots of features built-in and ready to use. In the upcoming parts of this series, we will look into them more, so stay tuned!

Series Navigation<< API with NestJS #1. Controllers, routing and the module structureAPI with NestJS #3. Authenticating users with bcrypt, Passport, JWT, and cookies >>

58 Comments

Oldest

Newest Most Voted

Inline Feedbacks

View all comments

Kuba

4 years ago

I like the series but posts tend to be really chaotic and missing some steps/vital information. Like here – where does docker start pgadmin ?Or you define the post entity, and then check the table structure in pgadmin, but we’ve never actually run anything yet. And you can’t run the server at this step, since the rest of the app was not updated (post.service for instance).

Author

Marcin Wanago

4 years ago

Reply to Kuba

I’m glad you like the series. Thanks for the feedback.
Pgadmin is defined in the docker-compose.yml file shared at the top of the article.

sujana pathuri

3 years ago

Reply to Marcin Wanago

Is it have inbuilt retry functionality to connect with the database in case of any error? if it has, may I know how it is working b/w node_modules @nestjs/typeorm, typeorm, pg?

Hossein

4 years ago

Thanks for this great article. It helps much.
I have two questions.

1. There is any way that automates the creation of the DB?
It seems that we should write our query manually, and I think it’s not much interested that do the exact same thing when we want to deploy it on real servers or event Netlify.

2. How to have only one .env file in dockerized projects?
I’m working on a dockerized project that some variables are shared between them. I don’t want to have separated .env files for each project.

Thanks and best of luck.

Alex

4 years ago

Reply to Hossein

2: There are env_file option for docker-compose. You can specify the same .env file for each service.

Hossein

4 years ago

Reply to Alex

Thanks.

Author

Marcin Wanago

4 years ago

Reply to Hossein

What exactly do you mean by creation of the database?

Last edited 4 years ago by Marcin Wanago

Hossein

4 years ago

Reply to Marcin Wanago

Actually, it was a misunderstanding from me (:
Sorry for that.

JBM

8 months ago

Reply to Hossein

Can you explain what is your misunderstanding? I think I have the same problem of comprehension than yours and it results with an ERROR [TypeOrmModule] Unable to connect to the database. Retrying (3)…
error: database “admin” does not exist.

Itunedy

3 years ago

Thank Wanago so much for this awesome series. I really love them and they help me a lot.

I have a question about your docker-compose please?

I see you have create services for “postgres”, “pgadmin”, that’s really good. But I don’t see that you create a service for “Nest server API”.

So if you run server normally with “yarn start:dev” for example, how is your server connect with docker container postgres ?

In my case, I need to create other service for server API in docker-compose (and run with Dockerfile). And I run them together with docker-compose up/build.

Thanks so much for your time.

Bhargav Gohil

2 years ago

Reply to Itunedy

I wanted to ask, how you linked the postgres with web server in docker. and you how you given the docker env for postgres connection in images filesystem?

Dmitry

2 years ago

Reply to Itunedy

ports:
– “5432:5432”

Means that the database will be able to handle connections from host machine (localhost:5432), so yes, node app on host machine will be able to connect to dockerized database. If you want to run the whole app in containers, just make sure you use the same network in docker-compose, and use container name as hostname for database (postgres:5432)

More info about docker networking available in docker documentation.

anh

1 year ago

Reply to Dmitry

i am using ubuntu, after running docker compose, how do i use PG admin ? where can i use PG Admin like local ?

Author

Marcin Wanago

1 year ago

Reply to anh

pgAdmin is available at http://localhost:8080/ if you are running docker-compose properly with the configuration mentioned in this article.

-2

Shivraj Nag

1 year ago

Reply to Marcin Wanago

Hi Marcin, what’s the credentials for the pgAdmin that is running on http://localhost:8080/ ? I tried using my local machine pgAdmin password and credentials from .env file of this project, but it throwing invalid credentials?

DpOriginals

3 years ago

find this amazing blog in google. nice content, thank you!

Alex

3 years ago

Hello, cant run service and have a Error on this steps

” [ExceptionHandler] Nest can’t resolve dependencies of the PostsService (?). Please make sure that the argument PostRepository at index [0] is available in the AppModule context.”

it’s normally?

Danny P

2 years ago

Reply to Alex

I expect this is no longer an issue for you being a year old comment but for the sake of others with similar issue:
Remember to add PostsService to the ‘exports’ array of your PostsModule. i.e.

@Module({

imports: [TypeOrmModule.forFeature([Post])],

controllers: [PostsController],

providers: [PostsService],

exports: [PostsService],

})

export class PostsModule {}

Yiannis

3 years ago

Great series, just started applying the tutorials to a demo course, thanks Marcin! I only had a couple of issues in my local env. Had to change the following lines or I would get errors
database.module.ts

1	entities: [__dirname + '/../*/.entity{.ts,.js}'],

posts.service.ts constructor

1	private postsRepository: Repository<Post>,

Alex

3 years ago

Reply to Yiannis

How you change that?

Yiannis

3 years ago

Reply to Alex

Hey Alex, in the tutorial above there are the original lines that were posted. I commented with the changes I made.

Brahianpdev

2 years ago

Reply to Yiannis

You save my! Thanks a lot <3

Aleksei

3 years ago

In pgAdmin, we can check a query equivalent to what TypeORM did for us under the hood.

Starting from this point – couldn’t find out where, when and how did the TypeORM worked for us. I mean – i suppose that it’s assumed that at that moment there should be a tables created but i can’t see none of them.

Have i missed something? Or the author meant that some actions should be taken by a reader himself?

Thanks.

Author

Marcin Wanago

3 years ago

Reply to Aleksei

TypeORM should create appropriate tables when you run the application assuming you have the synchronize flag turned on.

Fengwei

3 years ago

Reply to Marcin Wanago

Hi Wanago, When I login to pgAdmin, and expand the Service icon on the treeview to the left of the pgAdmin user interface, there is nothing there. Is there anything I have missed?

Mihai

3 years ago

Reply to Fengwei

@Fengwei did you manage to figure out what was wrong? I have the same issue…

Last edited 3 years ago by Mihai

Aidyn

2 years ago

Reply to Mihai

Maybe I’m late to the party, but pretty sure that it will be helpful for other guys. So the issue is that you run pgadmin, but you should also create connection to server. I resolved this issue by adding this lines to docker-compose file,
networks:
– postgres
environment:
– POSTGRES_HOST_AUTH_METHOD=trust
hostname: postgres,

docker-compose up , then go to localhost:8080, and you need to create the connection by clicking to register server, give the name of the server(whatever you want, for example nestjs), after that go to the connection tab, fill hostname/address with the hostname you provided to docker-compose file(postgres in our case),
so the form should look like this,
hostname/address: postgres
port:5432
maintenance database: postgres
username: admin,
password: admin,
role: ”,
service:”.
Click save, and you should see that connection is established and on left panel should appear server called nestjs

Navninder

2 years ago

Reply to Aleksei

You will need to login to the PostgreSQL database using pgAdmin. TypeOrm will automatically create the tables if the synchornize option is set to true. I host my PostgreSQL on AWS RDS and I can view and query anything using pgAdmin. It is a great tool. It is not possible with Nest to view the raw tables. You may use querybuilder to get the raw entities but I have never used them.

Justin

3 years ago

Thanks for this great article. Got one question.
When I run npm ran start:dev, it typeorm would create table based on the entities, right?
I connected the pgadmin and didn’t see anything. Is it right?

Last edited 3 years ago by Justin

Justin

3 years ago

Reply to Justin

I figured out there is a stupid mistake I made. Now, everything works. Thanks

Last edited 3 years ago by Justin

Achref

3 years ago

Reply to Justin

hey Justin, I have the same issue. How did you resolve that please?

Abner Simões

3 years ago

Reply to Justin

when connecting pgadmin, use the address “postgres” instead of “localhost”

Danny P

2 years ago

Reply to Abner Simões

I set my HOST envvar to ‘host.docker.internal’ in order for TypeORM to successfully connect. Couldn’t get a connection through ‘localhost’ or ‘postgres’

Alessandro

3 years ago

Hi Marcin,
thanks a lot for this tutorial.
I have some problem when I run npm run start because I receive this error:
—————————————————————————————————

1 2	[Nest] 22384 - 07/04/2021, 09:47:54 [TypeOrmModule] Unable to connect to the database. Retrying (1)... +249ms error: autenticazione con password fallita per l'utente "admin"

—————————————————————————————————

I can say you that I’m able to connect to postgresql via CLI; here some log:
—————————————————————————————————

# psql nestjs admin

psql (13.2 (Debian 13.2-1.pgdg100+1))

Type "help" for help.

nestjs=# admin

nestjs-# \conninfo

You are connected to database "nestjs" as user "admin" via socket in "/var/run/postgresql" at port "5432".

nestjs-# \z

Access privileges

--------+------+------+-------------------+-------------------+----------

(0 rows)

nestjs-#

—————————————————————————————————

I have tryed also you branch part-2 but I receive the same error.
How can I fix it?

thanks in advance

Navninder

2 years ago

Reply to Alessandro

You can fix it by allowing access to the database. You may have restricted it by using private domain wherever you are hosting your database. This happened to me as well when I used AWS RDS. I had to change the policies for allowing accessing to the databse with a public URL

Alessandro

3 years ago

Hi Marcin,
I discovered the problem: I had a previous local installation of Postgresql, so when typeOrm tryed to connect to Dockerzied Postgresql I had the error.
I uninstalled Postgresql on my local machine and all work.
Maybe at the beginning of this lesson, you could give an hint to remove any previous installation of Postgresql.
You can ignore my previous message.

Thank you.

Vladimir

3 years ago

Thanks a lot for this article? Do you have any experience with Sequelize ORM? I have some and It seems very inconvenient to use because of lack of query-builder and Typescript (written on Javascript, extra package required). Looking forward to use TypeORM. If you have Sequelize experience, could you please compare Sequelize and TypeORM?

Isaac

3 years ago

Thanks for this article, but I am yet to see how one2one relationships are handled here.

Константин

3 years ago

Hi
How can we automatically generate and run migrations when application starts with the database module?
I try to do so but it didn’t work out (

Elves Brito

2 years ago

I’m really enjoying it is a different approach than just following a video and playing it. Congratulations and I dare to suggest the creation of a course perhaps in this same footprint and perhaps with some deliberate mistakes to break your head a little. After all, that’s what we’re going to find on the market.

Oleh

2 years ago

Why should we use synchronize: true flag for DatabaseModule? How can we use migrations?

Navninder

2 years ago

Reply to Oleh

If set to false. You will not be able to create new columns in the entities. This is done to restrict users from modifying the entities when in production environment.

baked-potato

2 years ago

First of all, I’d like to say big Thank You to Marcin for producing such a cool tutorial!

Now I’ll share a few issues that I encountered with this particular post.

1) There is an issue with docker-compose config and macOS (Catalina or newer). It turns out that root path (“/”) is not writable so docker-compose is not able to mount “/data/postgres” or “/data/pgadmin” as a volume. So I replaced them with “/var/tmp/docker/<whatever-name>” and it worked fine. It looks like this:

1 2	volumes: - /var/tmp/docker/pgadmin:/root/.pgadmin

2) Regarding the connection to database via pgAdmin, this comment was helpful.

3) There are typos in code examples. Please refer to this comment.

4) When you initially run your app and connect to database (via pgAdmin or somehow else), there is not going to be any “post” table. It will be created lazily when you push first data to it.

Finally if someone lacks instructions regarding database and pgAdmin setup, the workflow is as follows. First, run “docker-compose up” in the project directory and wait till everything is started. Then, build the app and run it. Now you should be good:)

dennis

2 years ago

I’m getting this problem
invalid length of startup packet.
what could be the solution

Omer

2 years ago

I really wished to follow your tutorials, since you cover a lot, but they are too messy.
You probably didn’t try to follow your own tutorial and see if stuff works / does it make any sense.

I’m wasting a lot of time on error fixing / looking up missing information and trying to make stuff work, and for now I’m just going to abandon it and find other tutorials that work and properly guide through this stuff.

Thanks for the effort, I’m sure you tried to put your heart into this – I hope to come back at another time and find it better.

Author

Marcin Wanago

2 years ago

Reply to Omer

Hi. If you have any issues, feel free to join our Discord and ask.
Have a good day 🙂
http://wanago.io/discord

Omer

2 years ago

Reply to Marcin Wanago

Thanks, appreciated. I just joined

Navninder

2 years ago

Reply to Omer

I am going to be creating a same tutorial just like Marcin’s. My tutorial will be focused on creating an email marketing application using the same technologies. I will try to improve as much as I can. When finished, I will post a comment here. You may give me a feedback?

CND

2 years ago

good, but your example code makes me hard to understand. I need to visit your GitHub repository to understand it.

constructor(

@InjectRepository(Post)

private postsRepository: Repository<PostEntity>

) {}

PostEntity is Post, you need to define the name more clear for class at post.entity.ts

Last edited 2 years ago by CND

Tom

1 year ago

Reply to CND

So what’s Post in InjectRepository(Post) ?

phardi

2 years ago

Thanks for this great article. I have an issue about synchronize to database, cause the config typeorm ‘synchronize: true’ but the database not created after run the code with no error. I had try change to this code but still not synchronize
entities: [
__dirname + ‘/../**/*.entity{.ts,.js}’,
],

Ahmad Sharif

2 years ago

const updatedPost = await this.postsRepository.findOne(id);

findOne(id)
no longer works like this the syntax probably updated or somthing else
now it is working like

findOne({
where: { id },
});

thanks me later <3

Author

Marcin Wanago

2 years ago

Reply to Ahmad Sharif

That’s true. I wrote a separate article about it:
API with NestJS #67. Migrating to TypeORM 0.3

Cheers!

kien

1 year ago

Hello, everyone can help me this error
throw new Error(Config validation error: ${error.message});
Error: Config validation error: “POSTGRES_HOST” is required.

Thank you very much!

Author

Marcin Wanago

1 year ago

Reply to kien

Hi. Did you create the .env file with the POSTGRES_HOST variable?

kien

1 year ago

Reply to Marcin Wanago

This is my .env file:

POSTGRES_HOST=localhost

POSTGRES_PORT=5432

POSTGRES_USER=admin

POSTGRES_PASSWORD=admin

POSTGRES_DB=nestjs

PORT=5000

John

1 year ago

Great

giserman001

1 year ago

The tutorial was awesome and I learned a lot