Deploying Express.js Applications

# CHAPTER 19

Deploying Express.js Applications #

1. Introduction #

2. Learning Objectives #

• Protect sensitive data using the dotenv package.

• Prepare a package.json file for production deployment.

• Differentiate between VPS and PaaS hosting options.

• Use a Process Manager (like PM2) to keep servers alive 24/7.

3. Beginner-Friendly Explanation #

4. Step 1: Environment Variables (.env) #

Install: npm install dotenv

Create a .env file in the root of your project:

PORT=8080
MONGO_URI=mongodb+srv://user:SuperSecretPassword!@cluster.mongodb.net/db
JWT_SECRET=MyUltraSecureKey123

CRITICAL: Add .env to your .gitignore file. It must never go to GitHub.

In index.js (At the very top):

require('dotenv').config();

// Now access secrets securely via process.env
mongoose.connect(process.env.MONGO_URI);
app.listen(process.env.PORT);

5. Step 2: Preparing package.json #

In package.json:

"scripts": {
  "start": "node index.js",
  "dev": "nodemon index.js"
}

*Note: Never use nodemon in production! It watches files for changes, which consumes too much memory. Only use standard node index.js.*

6. Hosting Options: Where to Deploy? #

• Shared Hosting (cPanel): Generally terrible for Node.js. Avoid if possible.

• PaaS (Render, Heroku, Railway): The modern standard for beginners. You link your GitHub repository. Every time you git push main, the platform automatically downloads your code, runs npm install, and turns on the server.

• VPS (DigitalOcean, AWS EC2): You rent a blank Linux computer. You must install Node, MongoDB, and configure firewalls manually via the command line. Highly powerful and cheap, but difficult.

7. Step 3: Deployment Workflow (PaaS Example) #

1. 1. Push your code to GitHub (without the .env file and without node_modules).

1. 2. Log into the PaaS dashboard and connect your GitHub repo.

1. 3. Because the .env file was ignored, the live server doesn't know your database password! You must manually type your Environment Variables into the PaaS dashboard's specific "Environment" settings panel.

1. 4. Click "Deploy". The PaaS runs npm run start automatically. Your API is now live!

8. Step 4: Using PM2 on a Linux VPS #

On your live Linux server:

npm install -g pm2
pm2 start index.js --name "my-express-api"

PM2 forces the Node app to run endlessly in the background. If the app crashes, PM2 detects it and instantly reboots it in milliseconds.

9. Best Practices #

• Cloud Databases: Do not install MongoDB on the same physical server as your Express application. If the server goes down, you lose everything. Use a managed database service like MongoDB Atlas. It gives you a connection string (MONGO_URI) that you simply paste into your .env file.

10. Common Mistakes #

• Hardcoding Ports: Hosting providers (like Heroku) dynamically assign a random port to your application via process.env.PORT. If your code says app.listen(3000), the deployment will fail immediately because the platform refuses to let you use port 3000. Always use app.listen(process.env.PORT || 3000).

11. Exercises #

1. 1. Explain why the .env file must be added to .gitignore. If it is ignored, how does the production server know what the database password is?

12. Coding Challenges #

• Challenge: Audit your theoretical index.js file. Replace every instance of a hardcoded password, secret key, or port number with the appropriate process.env.VARIABLE_NAME syntax.

13. MCQs with Answers #

14. Interview Questions #

• Q: Explain the purpose of Environment Variables in a Node.js application. Provide examples of three specific pieces of data that should *always* be stored in .env rather than hardcoded.

• Q: Compare deploying an Express application to a raw VPS versus deploying it to a PaaS (like Heroku or Render). What are the trade-offs regarding control and ease of use?

15. FAQs #

16. Summary #

17. Next Chapter Recommendation #