This lesson covers the deployment of a Nest.js project to Railway, detailing the necessary configurations. It requires setting up distinct 

 files for development and production environments. Nest.js best practices include using environment-specific configuration files to manage different settings for development, testing, and production, ensuring sensitive data is not exposed. Proper management of environment variables is crucial for security and flexibility in different deployment scenarios.

Step 1: Create New Account at the Railway

After creating an account at Railway you have to create a new project, connect your Github account with Railway

Step 3: add NODE_ENV in configuration file

, which is a best practice in NestJS for maintaining environment-based configurations, thereby facilitating easier management and scalability of the application’s settings.

---
title: Configure the Developer and Production Environment
privateVideoUrl: https://fullstack.wistia.com/medias/ja2b7eonhx
isPublicLesson: true
---

This lesson covers the deployment of a Nest.js project to Railway, detailing the necessary configurations. It requires setting up distinct `.env` files for development and production environments. Nest.js best practices include using environment-specific configuration files to manage different settings for development, testing, and production, ensuring sensitive data is not exposed. Proper management of environment variables is crucial for security and flexibility in different deployment scenarios.

### Step 1: Create New Account at the Railway

Create a new account at [Railway](https://railway.app/).

### Step 2: Create a new Project

After creating an account at Railway you have to create a new project, connect your Github account with Railway

### Step 3: add NODE_ENV in configuration file

The `NODE_ENV` has not been included in `configuration.ts`. Including it would enable access to `NODE_ENV` through `ConfigService`, which is a best practice in NestJS for maintaining environment-based configurations, thereby facilitating easier management and scalability of the application’s settings.

Haider Malik

Configure the Developer and Production Environment

In this lesson, we're going to prepare our application for deployment.

I'm going to teach you how to deploy NestJS application at railway.

You will also deploy your Postgres database at railway.

We're going to deploy our application, this one, this Spotify clone which we

Our application is using Postgres database with type or m.

I'm going to teach you how to deploy the complete application at railway.

First of all, you got to create a new project.

Make sure you deploy your project at GitHub repository.

First of all, we have to do a little bit configuration.

When I will run the application in production, it should run this production.

If I'll be working at development environment, I'm going to work with local

I don't want to change in production level.

So we're going to configure a couple of settings.

We already created the .env.development.env.production, but it is not config

When my project is running in production mode, it should pick this production

I've already written down the validation in the env validation for node

I can say node env and I can get the value from process.

Now this variable is available for the config service.

I've already provided you the nastures deployment railway starter kit project.

You have to open it and run npm install to install all the dependencies.

Now we have to configure the env file path in app module.

I can say, please get the value from process.env.node env.

Or you can say, get the path from the current working directory and you can

Get the path from the current working directory and slash dot.

Please get the working directory and find the env.production file or env.

We have to set the script or we have to set the development environment in our

For the def, I can say, I want to mention node env to development.

Here we have to set the production value.

When you run the application with production, how can I test it in the main.ts

I can say, console.log config service.get.

My application is running in the development environment.

If I run the application in production environment, when you see the production

You can see that my application has crashed.

An instance of environment variable has failed.

If I copy this configuration, what will happen?

You can see that my application is working fine now.

But we will replace these configurations with railway postgres configuration.

We will be able to make sure that we can get the data.

Learn

The newline Guide to Building Your First GraphQL Server with Node and TypeScript

Teach

Amelia Wattenberger

Author of Fullstack D3

Community

Masterclasses

Tutorials

Fullstack React with TypeScript