Creating a Node.js Application Container

When creating a Node.js container there are a few ways to go about it, depending on your application and needs.

In this article we will cover setting up a standalone Node.js application with custom ports. We will also talk about using an Nginx proxy to handle web assets, images and resources when your Node.js application is used as a web service.

  1. When logged in to the SiteHost Control Panel, click the Containers module from the menu on the left.
  2. Click the Add Container option in the upper right corner of the page.
  3. Select Service Image from the navigation tabs.
  4. Choose the Node.js image and select which version you want to use.
  5. Choose a name for your container.
  6. Choose the Port number and Protocol conveniently. By defualt containers on a server can access the Node.js container through port 8080. Tick the Publish check box if you require the port to be accessible from a remote location (not only on the server).
  7. Type in the SSH Username and SSH Password fields to create a SSH/SFTP user with access to the Node.js Container.
  8. Set Environment Variables filling in the Name and Value text fields.
  9. Click Deploy Container and check the deployment progress presented in the page header.

Once the container has been started, upload your files to the Container using your SSH/SFTP user. By default all Node.js containers will try and look for the file /container/application/app.js. If your Node.js application file is named differently or in another location, you can edit the configuration file located at /container/config/supervisord.conf changing the command line accordingly.

command=/usr/local/bin/node /container/application/app.js

Restart the Container using the Control Panel to apply the configuration changes.

Nginx Proxy

If your Node.js application is used as a web application, you may need a proxy in front to handle static assets, images and other resources. If that's the case, you can start by creating an nginx proxy just like any other web container.

Once you have created your nginx proxy Container, edit the nginx configuration file located at the path /container/config/nginx/sites-available/default. You should see the commented out lines as per the below:

#upstream nodejs44 {
#        server NODE_CONTAINER_HOSTNAME:8080;
#}
#        proxy_pass http://nodejs44/;

Uncomment the lines above, replace the NODE_CONTAINER_HOSTNAME with the hostname for your Node.js Container and save the configuration file. The Node.js hostname can be found within the Container management page in the SiteHost Control Panel. Reboot the nginx Container to apply the configuration changes.

Deugging your Node.js application

The standard output messages should be logged to the path /container/application/logs/supervisor/nodejs-stdout.log whereas the standard error stream should be logged to the file located at /container/application/logs/supervisor/nodejs-stderr.log.

If you apply changes to your application and can't see the changes live, try restarting the nginx proxy and browsing to your app using the incognito or private window.