How to Deploy NodeJs-express app with a static front-end in a pug on Elestio

So you made a static full stack frontend pug with nodejs backend application and want to deploy it to the cloud 🚀

You probably heard about Kubernetes (and all its complexity) or various options to deploy your apps like Heroku, Render Fly, or Railways. They all have something in common, those products are building your own source code on every commit from your GIT repository.

Elestio is doing the same ...  but different! Instead of deploying your app to a shared cluster, we deploy to dedicated VMs.

In this tutorial, we will deploy a simple NodeJs-express app with a static front-end in a pug that the backend in nodejs was created using the npm init command. You can use any existing application, create a new one with npm init, or simply fork and use our example by following the link.

To learn more about the elestio CI-CD, go here.

If you're new, sign up for Elestio, otherwise, login to your existing account.

Deploy a NodeJs-express app with a static front-end in a pug with CI/CD to the cloud

Step 1:

Go to CI/CD from the left sidebar.

Step 2:

Now, select the deployment source.

Screenshot 2022-11-02 185434.png

In this tutorial, I'm deploying using GITHUB, but you can also use GITLAB if you have a project there.

Step 3:

Select the repository.

If you have already authenticated your GITHUB or GITLAB account in ci-cd for repository access, you can choose the desired repository to deploy directly. Otherwise, you must first authenticate your GIT account with elestio ci-cd for repository access.

Screenshot 2022-11-03 181459.png

Step 4:

Choose Deployment Targets

Screenshot 2022-11-02 191657.png

Elestio offers two types of deployment targets "Deploy on a  new VM" and "Deploy on an existing VM".

You are allowed to set up n pipelines on each elestio Ci-CD target/VM. According to the project configuration you select and the project you're deploying, the number of pipelines varies.

If you want to deploy these projects as a pipeline on a new Target/VM or don't have any installed targets, choose "Deploy on a new VM." If you already have any installed or previously configured ci-cd targets/VMs, choose "Deploy on an existing VM," and then choose the existing target from the targets dropdown.

Follow the steps below only if you select "Deploy on a new VM," otherwise click the next button to proceed.

CI/CD Pipelines by Elestio are available with our 5 cloud partners (AWS Lightsail, Digital Ocean, Vultr, Linode & Hetzner) in 85 locations over 27 countries but also on any cloud (AWS, Azure, Google, Oracle, ...) and on-premise with BYOVM.

  • Select Service Cloud RegionScreenshot 2022-11-02 194242.png
  •  Select Service PlanScreenshot 2022-11-02 194721.png

  • Now Customize the target name and project (where the CICD Target will be created). 

Screenshot 2022-11-03 181554.png

If you want to deploy it with a different name and a different project, you can customize it. By default, we configure it with a dynamic target name and the current project.

Step 5:

Configure your Project

Screenshot 2022-11-03 181630.png

You can configure the project details by filling up the project name, branch, run time, version, framework, and root directory.

Screenshot 2022-11-03 191022.png

You can configure your project install, run, and build commands in the Build and output setting.

Screenshot 2022-11-02 201628.png

The configuration of life cycle scripts is always optional; they should only be used if you want to execute a specific command before and after building your project. Otherwise, leave them empty.

Screenshot 2022-11-03 191114.png

You can list all of your project's API keys and secrets here if they were saved in ENV

Screenshot 2022-11-02 202142.png

Screenshot 2022-11-02 202154.png

The final step is to configure the exposed port and reverse proxy settings. You can specify the port on which your project will run here.

If your project includes elestio.yml, Elestio will auto-fill all of these fields. As in this tutorial, we're using our NodeJs elestio example, so you can see in the above images that all of our fields are auto-filled.

A sample elestio.yml for NodeJs is shown below. check it out on github

    runTime: 'NodeJs'
    version: ''
    framework: 'NoFramework'
    buildCommand: ''
    buildDir: ''
    runCommand: 'npm start'
    installCommand: 'npm install'
    icon: "public/images/nodejs.svg"
    screenshot: "public/images/screenshot.jpg"
  - protocol: "HTTPS"
    targetProtocol: "HTTP"
    listeningPort: "443"
    targetPort: "3000"
    targetIP: ""
    public: true
    path: "/"
    isAuth: false
    login: ""
    password: ""
    -  key: 'ENV'
       value: 'production'
    -  key: 'PORT'
       value: '3000'
  - url: "https://[CI_CD_DOMAIN]"
    label: "Website"

Step 6:

Click the Create CI/CD pipeline button to deploy your pipeline.

Screenshot 2022-11-02 203203.png

In a couple of moments, your application was successfully deployed on elestio 🚀.

Screenshot 2022-11-03 193307.png