Getting Your Node.js Application Production-Ready

By default, only SSH/SFTP (port 22), HTTP (port 80), and HTTPS (port 443) are open on your DigitalOcean droplet. To review and make changes to your firewall settings, use the command `sudo ufw status`. Additionally, it is recommended that you set up a non-root user for day-to-day use.

To get production-ready, build out the URL directory structure you need by mapping applications to URL paths using the reverse proxy method in nginx. This can be done by scheduling your Node.js apps to run concurrently and mapping them to HTTP/HTTPS URLs in the nginx config.

For example, if you have a Node.js app that runs on port 3000, use PM2 to schedule it to run at boot time on an internal port of your choice. Then, map that port to an HTTP URL by running `nano /etc/nginx/sites-available/default` and adding another location block.

To launch your app, call `pm2 start`, then map the port your app runs on to an HTTP URL by running `nano /etc/nginx/sites-available/default` and adding another location block. If you're not using source control, you can directly upload the files to your droplet using SFTP.

Alternatively, SSH into your Droplet and use Git to clone your Node.js code onto the droplet. Make sure to run `pm2 delete hello` to stop running this script and `pm2 save` to stop it from running on Droplet boot.

To see a list of all scheduled scripts, run `pm2 list`. If you want to kick the tires right now, try some of these things: This app is running at port 3000, and is being served to you by nginx, which has mapped port 3000 to be served as the root URI over HTTP (port 80) - a technique known as a 'reverse proxy.'

Fouad Mods

This article was written using 'fouad mods'.

Fouad mods