One place for hosting & domains


      Deploying a Node App to Digital Ocean


      There are various platforms that help with deploying Node.js apps to production.

      In this tutorial, we’ll be looking at how to deploy a Node.js app to DigitalOcean. DigitalOcean compared to these other platforms is cheaper and you also can log on to your server and configure it however you like.

      You get more control over your deployment and also it’s a great experiment to see exactly how Node apps are deployed to production.

      This tutorial assumes the following:

      Let’s quickly build a sample app that we’ll use for the purpose of this tutorial. It going to be a pretty simple app.

      1. // create a new directory
      2. mkdir sample-nodejs-app
      3. // change to new directory
      4. cd sample-nodejs-app
      5. // Initialize npm
      6. npm init -y
      7. // install express
      8. npm install express
      9. // create an index.js file
      10. touch index.js

      Open index.js and paste the code below into it:

      const express = require('express')
      const app = express()
      app.get('/', (req, res) => {
        res.send('Hey, I\'m a Node.js app!')
      app.listen(3000, () => {
        console.log('Server is up on 3000')

      You can start the app with:

      1. node index.js

      And access it on http://localhost:3000.

      You should get:


      Hey, I'm a Node.js app!

      The complete code is available on GitHub.

      Now let’s take our awesome app to production.

      Login to your DigitalOcean account and create a new droplet (server). We’ll be going to with One-click apps. Select Node.js as shown below:

      Next, we’ll choose the $10 plan. Though the task list app will work perfectly on the $5 plan, but we won’t be able to install the npm dependencies because the npm requires at least 1GB RAM for installing dependencies. Though there is a way around this by creating swap memory which is beyond the scope of this tutorial.

      Next, select a datacenter region, we’ll go with the default:

      Next, add a new SSH key or choose from the existing ones that you have added. You can get your SSH key by running the command below on your local computer:

      1. cat ~/.ssh/

      The command above will print your SSH key on the terminal, which you can then copy and paste in the SSH Key Content field. Also, give your SSH key a name.

      Finally, choose a hostname for the droplet and click the Create button.

      After a couple of seconds, you’ll have your new server up and running on Ubuntu 16.04 and NodeJS version 6.11.2. Note the IP address of the server as we’ll be using it to access the server.

      Before we start configuring the server for the task app, let’s quickly create a non-root user which we’ll use henceforth for the rest of the tutorial.

      Note: As a security measure, it is recommended to carry out tasks on your server as a non-root user with administrative privileges.

      First, we need to log in to the server as root. We can do that using the server’s IP address:

      1. ssh root@SERVER_IP_ADDRESS

      Once we are logged in to the server, we can move on to create a new user:

      1. adduser mezie

      This will create a new user called mezie, you can name the user whatever you like. You will be asked a few questions, starting with the account password.

      Having created the new user, we need to give it administrative privileges. That is, the user will be able to carry out administrative tasks by using sudo command.

      1. usermod -aG sudo mezie

      The command above adds the user mezie to sudo group.

      Now the user can run commands with superuser privileges.

      You need to copy your public key to your new server. Enter the command below on your local computer:

      1. cat ~/.ssh/

      This will print your SSH key to the terminal, which you can then copy.

      For the new user to log in to the server with SSH key, we must add the public key to a special file in the user’s home directory.

      Still logged in as root on the server, enter the following command:

      1. su - mezie

      This will temporarily switch to the new user. Now you’ll be in your new user’s home directory.

      Next, we need to create a new directory called .ssh and restrict its permission:

      1. mkdir ~/.ssh
      2. chmod 700 ~/.ssh

      Next, within the .ssh directory, create a new file called authorized_keys:

      1. touch ~/.ssh/authorized_keys

      Next, open the file with vim:

      1. vim ~/.ssh/authorized_keys

      Next, paste your public key (copied above) into the file. To save the file, hit ESC to stop editing, then :wq and press ENTER.

      Next, restrict the permissions of the authorized_keys file with this command:

      1. chmod 600 ~/.ssh/authorized_keys

      Type the command below to return to the root user:

      1. exit

      Now your public key is installed, and you can use SSH keys to log in as your user.

      To make sure you can log in as the new user with SSH. Enter the command below in a new terminal on your local computer:

      1. ssh mezie@SERVER_IP_ADDRESS

      If all went well, you’ll be logged in to the server as the new user with SSH.

      The rest of the tutorial assumes you are logged in to the server with the new user created (mezie in my case).

      We are going to clone the app unto the server directly in the user’s home directory (that is, /home/mezie in my case):

      1. git clone

      Next, we install the dependencies:

      1. cd sample-nodejs-app
      2. npm install

      Once the dependencies are installed we can test the app to make sure everything is working as expected. We’ll do so with:

      1. node index.js

      The app is listening on port 3000 and can be accessed at http://localhost:3000. To test the app is actually working, open a new terminal (still on the server) and enter the command below:

      1. curl http://localhost:3000

      You should get an output as below:

      1. Hey, I'm a Node.js app!

      Good! The app is up and running fine. But whenever the app crashes we’ll need to manually start the app again which is not a recommended approach. So, we need a process manager to help us with starting the app and restarting it whenever it crashes. We’ll use PM2 for this.

      We’ll install it globally through npm:

      1. sudo npm install -g pm2

      With PM2 installed, we can start the app with it:

      1. pm2 start index.js

      Once the app is started you will get an output from PM2 indicating the app has started.

      To launch PM2 on system startup or reboot, enter the command below:

      1. pm2 startup systemd

      You’ll get the following output:

      1. [PM2] Init System found: systemd
      2. [PM2] To setup the Startup Script, copy/paste the following command:
      3. sudo env PATH=$PATH:/usr/local/bin /usr/local/lib/node_modules/pm2/bin/pm2 startup systemd -u mezie --hp /home/mezie

      Copy and run the last command from the output above:

      1. sudo env PATH=$PATH:/usr/local/bin /usr/local/lib/node_modules/pm2/bin/pm2 startup systemd -u mezie --hp /home/mezie

      Now PM2 will start at boot up.

      Next, we’ll install Nginx as the webserver to be used for reverse proxy which will allow us to access the app directly with an IP address or domain instead of tacking port to the IP address.

      1. sudo apt-get update
      2. sudo apt-get install nginx

      Because we chose 1-Click Apps while creating our Droplet, ufw firewall is set up for us and running. Now, we need to open the firewall for only HTTP since we are not concerned with SSL in this tutorial:

      1. sudo ufw allow 'Nginx HTTP'

      Finally, we set up Nginx as a reverse proxy server. To this, run:

      1. sudo vim /etc/nginx/sites-available/default

      Within the server block you should have an existing location / block. Replace the contents of that block with the following configuration:

      // /etc/nginx/sites-available/default
      location / {
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-NginX-Proxy true;
        proxy_pass http://localhost:3000;
        proxy_set_header Host $http_host;
        proxy_cache_bypass $http_upgrade;
        proxy_redirect off;

      Save and exit vim.

      Test to make sure there are no syntax errors in the configuration by running:

      1. sudo nginx -t

      Then restart Nginx:

      1. sudo systemctl restart nginx

      Now you should be able to access the app with your IP_ADDRESS. You should get something similar to the image below:

      In this tutorial, we have seen how to deploy a Node.js app to DigitalOcean. We also saw how to setup a reverse proxy server with Nginx.

      Deploying Microservices as Kubernetes DaemonSets and Jobs

      How to Join

      This Tech Talk is free and open to everyone. Register below to get a link to join the live stream or receive the video recording after it airs.

      August 25, 202111 a.m.–12 p.m. ET / 3–4 p.m. GMT

      About the Talk

      Migrating containerized workloads to Kubernetes? See when and how to use Kubernetes
      DaemonSets and Jobs to deploy your application or microservice.

      What You’ll Learn

      • How to distinguish between the different use cases for Kubernetes DaemonSets and Jobs
      • How to create a YAML manifest for a DaemonSet and Job
      • How to create and inspect a Kubernetes DaemonSet and Job

      This Talk Is Designed For

      • Anyone running containerized workloads in a non-Kubernetes environment
      • Anyone looking to gradually migrate to Kubernetes


      • You have containerized an application or microservice
      • You have basic knowledge of containers and Kubernetes


      Kubernetes for Full-Stack Developers: Community Curriculum and eBook
      Kubernetes on DigitalOcean: Docs and Quickstart
      How to Deploy Your Application or Microservice on Kubernetes
      Kubernetes Docs: DaemonSet
      Kubernetes Docs: Jobs

      To join the live Tech Talk, register here.

      Source link

      Deploying MongoDB With Redundancy

      Part of the Series:
      MongoDB Security: Best Practices to Keep Your Data Safe

      MongoDB, also known as Mongo, is a document database used in many modern web applications. As with any database management system, it’s critical that those responsible for managing a Mongo database adhere to the recommended security best practices, both to prevent data from being lost in the event of a disaster and to keep it out of the hands of malicious actors.

      This series of conceptual articles provides a high-level overview of MongoDB’s built-in security features while also highlighting some general database security best practices.

      No matter what precautions you or your cloud provider take to prevent them, computers are always at risk of hardware failure. An important part of managing any computer system, not just a MongoDB installation, is to make regular backups of your important information. By taking and storing backups of your data, you can restore your application to working order if your database server crashes and your original data is lost.

      Just as you should regularly back up your MongoDB data, it’s equally important that you store those backups in a separate location from the server hosting your database. If you were to store your backups in the same data center as your database, both the database and your backups would be unavailable if the data center were to experience a failure and you wouldn’t be able to use the backups to get your application back online.

      Replication is a practice that’s similar to making backups: where making a backup involves taking a point-in-time snapshot of all the data held in a database, replication involves constantly synchronizing data across multiple separate databases. It’s often useful to have multiple replicas of your data, as this provides redundancy in case one of the database servers fails and can also improve a database’s availability and scalability, as well as reduce read latencies. In MongoDB, a group of servers that maintain the same data set through replication are referred to as a replica set.

      The official documentation recommends that any Mongo database used in a production environment be deployed as a replica set, since MongoDB replica sets employ a feature known as automatic failover. This means that if the primary fails and is unable to communicate with the secondary members for a predetermined amount of time, the secondary members will automatically elect a new primary member, thereby ensuring that your data remains available to your application or the clients that depend on it.

      Source link