How to Set Up Node.js on Linode with ORIV?

Node.js is a powerful runtime that enables fast, scalable and modern web applications. With ORIV, you can easily setup Node.js on the Linode server in ORIV. ORIV makes hosting and managing Node.js sites easy, so you can focus on building great websites.This guide will show you how to set up Node.js on Linode using ORIV.

​

How to Integrate And Setup Linode Server with ORIV?

This guide shows how to set up the Linode server in ORIV. Follow the steps to quickly launch, configure and start your cloud journey.

​

Step 1: Sign Up/Login With ORIV

First, you will need to visit the ORIVwebsite and you have to sign up for ORIV with your credentials. If you already have an account please visit our login page.  Now you are ready to set up your server with Digital Ocean in ORIV.

​

Step 2: Create Your Linode Server in ORIV

After logging in to your ORIV account, start by adding a new server by clicking on the “Add New Server” button from your dashboard. The next screen will provide the list of our available server providers. For tutorial purposes, we will create a Linode server and for that select the Linode option. 

​

Step 2: Authorize Your Linode Account

We have made it easier and safer for you to connect ORIV with your Linode account. Now provision a new Linode server, click ‘Authorize on Linode’ during the setup, and you will be redirected to Linode to grant permission to your account. It is a straightforward and hassle-free process to set up your server with Linode.

​

Step 3: Connect the Account & Add the Necessary Information

You will be taken to the server creation page after successfully integrating your Linode account and your server will be connected with ORIV. Now you need to provide the ‘Server name’, your preferred ‘Server Size’ (CPU, RAM, storage), the ‘Region’ nearest to you and your visitors, and then select the ‘Database Server’ from MySQL and MariaDB. Note: We recommend at least a 2GB/ 1 shared CPU server for 10-20 brochure sites with cache enabled. And for a site whose pages cannot be cached (e.g. WooCommerce site) we recommend a 4 GB / 2 dedicated CPUs server. Next, choose the web server stack from ‘NGINX’ or ‘OpenLiteSeed’ as your requirements and click on the ‘Next’ button to proceed with the server creation process. It will start creating a Linode server with ORIV within a while and if you go to the ‘Servers’ from the menu you can see your created server and create as many sites as you want under this server.

​

How to Set Up Node.js on Linode with ORIV

ORIV provides an intuitive interface that allows you to easily deploy, manage and scale your Node.js applications directly from your Git repository without worrying about manual setup or infrastructure maintenance. Follow the guide to deploy your Node.js application easily on Linode with ORIV:

​

Step 1: Choose the Application

To begin deployment, click on the ‘Add New Site’ button from the dashboard. You will then be asked to ‘Choose a Server to add Site’ from the dropdown. You must select the Linode server you set up in ORIV from this dropdown. Next, you will see options such as ‘WordPress’ and ‘Custom PHP’. Go to the ‘Node.js’ option from the tab. After that, choose the ‘Choose a Git Repository’ option to import your Node.js application using a Git provider.

​

Step 2: Set Up Domains

The ‘Domains’ tab allows you to configure your site’s domain. You can either create a ‘Demo Site’ or a ‘Live Site’. For this documentation, we’ll proceed with the ‘Demo Site’ option and click ‘Next’ to continue.

​

Step 3: Configure Node.js Application

In the ‘Settings’ tab, you will find options to configure the Node.js version and manage site users. Adjust them according to your preferences. Next, you will see the ‘Server-Side Rendering App’ option. To proceed with a ‘Client-Side Rendering App’, keep the toggle off. To deploy a ‘Server-Side Rendered App’, toggle it on.

​

Client-Side Rendering (CSR):

If your application is built using frameworks like React or Vue that render content in the browser, keep the toggle off. In this mode, the server mainly serves static files and all rendering happens on the client side.

​

Server-Side Rendering (SSR):

If your Node.js application (for example, Next.js or Nuxt.js) renders pages on the server before sending them to the client, toggle this option on. This allows ORIV to configure the environment to support SSR processes properly. Here we are proceeding with deploying a ‘Server Side Rendered App’ option → Then you’ll need to provide a few essential details: ◽Port: Enter the port number your Node.js application listens on (e.g., 3000 or 8080). ORIV uses this port to connect incoming traffic to your app. ◽Start Command: Specify the command that runs your application (for example, npm start, node server.js, or yarn dev). This tells ORIV how to start your Node.js server after deployment. ◽Web Root Path: If your project’s main application files are located in a subdirectory (for instance, /app or /src), enter that path here. If your app is in the root directory, you can leave this field blank. Now, insert the ‘Port’ and ‘Start Command’ in the respective fields. You can also specify a ‘Web Root’ Path for your application. In the following step, you can choose one of the database options ‘No Database’, ‘Add an Existing Database’, ‘Create a New Database’ directly on the server. Once selected, click ‘Next’.

​

Step 4: Insert Git Repository Credentials

In the “Git Repo” tab, you will find three repository options: ‘Private Repository (Manual SSH URL)’, ‘Public Repository (Manual HTTPS URL)’, ‘Connected Git Provider’. If you choose Public Repository (Manual HTTPS URL), enter your GitHub Repository URL and specify the Git Branch. Note: Copy the HTTPS URL from your GitHub repository dashboard. If you choose Private Repository (Manual SSH URL), enter your GitHub Repository SSH URL and specify the Git Branch. Note: Copy the SSH URL from your GitHub repository dashboard. In this document, we’ll deploy the project using the “Git Provider” option. Choose “Connected Git Provider” from the dropdown menu. From the “Select Git Provider” list, choose the connected account you want to use. Then, browse through the repositories, select the one you want to deploy and choose the specific branch of that project.

​

Step 5: Enable Push-to-Deploy

The next step is to enable automated deployment. Toggle on the ‘Enable Push to Deploy’ option. Copy the ‘Deployment URL’ provided here, you will need to insert it into your GitHub repository’s webhook settings.

​

Step 8: Run Deployment Script

Once the repository integration is complete, you can configure post-deployment actions. In the ‘Deployment Script’ field, enter any custom commands you want to execute after deployment. You can also select one of the example scripts provided. After configuring this, click ‘Next’ to continue. Next, you can specify the subdirectory where your .env file should be created in the “.env File Path” field. You can also enter the contents of your .env file in the “File Content” field.

​

Step 9: Confirm Deployment

The final step is to confirm and start the deployment. Click the ‘Start’ button to begin the process. You can monitor the deployment progress in real time. After deployment, a success message will appear. From there, access your site dashboard and visit your site to confirm your Node.js app is running on Linode server with ORIV.

​

Environment Editor for Node.js Application

The Environment section in ORIV allows you to customize configuration settings for your n8n instance. Just go to the ‘Environment’ option from the sidebar and adjust as you need then click on the ‘Save’ button.

​

SSR Configuration for Node.js application

If you are deploying an SSR application, you can update the ‘Application Port’, ‘Start Command’ later as well. Just go to the ‘SSR Configuration’ from the ‘Node.js’ Menu under the site dashboard and click on the ‘Update Configuration’ button. Setting up a Node.js application on a Linode server with ORIV is simple and efficient. After setting up or deployment, you can manage your app, update settings and push changes directly from your Git repository. Still stuck? Contact our support team for any of your queries.