PM2 backend deployment

Environment variables are loaded via src/env.ts (dotenv.config()). The .env file must live in the server working directory.

First-time setup

cd /var/www/your-app/server
git clone <your-nodejs-repo-url> .    # if not already cloned
npm install
npm run build
pm2 start dist/src/app.js --name nifty-backend --cwd /var/www/your-app/server
pm2 startup                          # follow printed command to enable boot start
pm2 save

Routine deploy

cd /var/www/your-app/server
git pull
npm install
npm run build
pm2 restart nifty-backend
pm2 save

Verification

pm2 status
pm2 info nifty-backend
pm2 logs nifty-backend --lines 100

Confirm working directory and env:

pm2 info nifty-backend | grep -E "exec cwd|script path"
pm2 env nifty-backend | grep -E "MONGO_URI|ZERODHA|PORT|SECRET"

Critical: PM2 --cwd must point to the folder containing .env. If env vars are missing, the process likely started from the wrong directory.

Alternative PM2 start

If dotenv does not load as expected:

pm2 start dist/src/app.js --name nifty-backend --cwd /var/www/your-app/server

The app imports ./env at startup, so the standard start command above is sufficient when cwd is correct. Environment is loaded via src/env.ts before other modules. PM2 must use the server directory as working directory.

cd /var/www/NiftyBankNifty/server
git pull
npm install
npm run build
pm2 restart nifty-backend
pm2 save

Verify PM2 cwd and env:

pm2 info nifty-backend | grep -E "exec cwd|script path"
pm2 env 1 | grep ZERODHA_API_KEY

Alternative PM2 start (optional): node -r dotenv/config dist/src/app.js with cwd set to the server folder.

Deployment

Environment

Zerodha Operations

Scripts

Verification

Cross-reference

First-time setup

Routine deploy

Verification

Alternative PM2 start

​First-time setup

​Routine deploy

​Verification

​Alternative PM2 start

​Zerodha auto-login deploy example

First-time setup

Routine deploy

Verification

Alternative PM2 start

Zerodha auto-login deploy example