Deploy examples & apps on Elestio using the “Import Third-Party Git Repository” feature
Tags: opensource, elestio, thirdparty, deploy
Published: 2023-10-11 13:04:13

---
title: Deploy examples & apps on Elestio using the “Import Third-Party Git Repository” feature
published: true
date: 2022-11-21 11:28:12 UTC
tags: opensource, elestio, thirdparty, deploy
canonical_url: https://elestio.hashnode.dev/deploy-examples-apps-on-elestio-using-the-import-third-party-git-repository-feature
---

This tutorial will walk you through the process of deploying GitHub, GitLab, or Bitbucket public repositories in CI/CD using our **Import Third-Party Git Repository** feature. In our example, well use a Simple JavaScript web application public repository, but you can deploy it, in the same way, using any public repository from **_GitHub_** , **_GitLab_** , or **_Bitbucket_**. 🚀

#### What is the Import Third-Party Git Repository?

A feature of Elestios CI/CD **Import Third-Party Git Repository** lets you deploy any type of public git repository from _GitHub_, _GitLab_, or _Bitbucket_ in the Elestio cloud.

#### What is the difference between Import Git Repository And Import Third-Party Git Repository?

Only public or private repositories that are already in your own git account can be deployed using the **_Import Git Repository_** feature. Depending on the deployment method you select-for example if you choose GITHUB-you can only deploy repositories that are already in your github account. On the other hand, you can deploy any only public repository from your or anyone elses account from github, gitlab, or bitbucket using the **Import Third-Party Git Repository** feature.

> _In these_ **_Import Third-Party Git Repository_** _features, Elestio will create a repository from your entered repository URL in your git account and 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.

> _To learn more about the elestio CI/CD, go_ [**here**](https://docs.elest.io/books/cicd-pipelines/page/overview?ref=blog.elest.io).

If youre new, sign up for [_Elestio_](https://dash.elest.io/?ref=blog.elest.io), otherwise, login to your existing account.

#### Deploy Any Public repository Apps to the cloud using the CI/CD Import Third-Party Git Repository feature.

#### Step 1:

Go to CI/CD from the left sidebar.

#### Step 2:

Now, select the deployment source.

![](https://cdn.hashnode.com/res/hashnode/image/upload/v1697005713967/d6ada74b-125c-40f9-b527-8ffa076ece60.png)

In this tutorial, Im deploying using GITHUB, but you can also use GITLAB if you want to deploy your repository there.

#### Step 3:

Click the Import a Third-Party Git Repository

![](https://cdn.hashnode.com/res/hashnode/image/upload/v1697005715602/80b17e62-bc57-48ce-aa85-2c76106aa2a3.png)

The URL of the public repository you want to deploy should now be entered here.

Now click the **_Continue_** button to proceed.

> _If you have already authenticated your GITHUB or GITLAB account in CI/CD for repository access, you can fill up the below details directly. Otherwise, you must first authenticate your GIT account with elestio CI/CD for repository creation into your account._

We require GIT authentication in order to create these example template repositories in your GIT account.

![](https://cdn.hashnode.com/res/hashnode/image/upload/v1697005717369/a729a57e-9054-4886-a88e-8b8691e08192.png)

Here you can check the checkbox **_Create private Git Repository_** if you want to make these repo private otherwise leave it unchecked and click the **_Next button_** for further steps.

#### Step 4:

Choose Deployment Targets

![](https://cdn.hashnode.com/res/hashnode/image/upload/v1697005719013/119a9c31-845f-4096-8e0e-13059d7852be.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 youre deploying, the number of pipelines varies.

If you want to deploy these projects as a pipeline on a new Target/VM or dont 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.](https://doc.elest.io/books/cloud-providers/page/byovm-bring-your-own-vm?ref=blog.elest.io)

![](https://cdn.hashnode.com/res/hashnode/image/upload/v1697005720527/f540b920-e3f7-438f-8db1-540fc7f7240b.png)

![](https://cdn.hashnode.com/res/hashnode/image/upload/v1697005721853/e4c96825-d64d-4644-bf99-c1ce1646925b.png)

![](https://cdn.hashnode.com/res/hashnode/image/upload/v1697005724047/700c582b-0b9a-488c-b018-d69ef8062e9c.png)

![](https://cdn.hashnode.com/res/hashnode/image/upload/v1697005725772/7cc90239-7178-4174-ac9f-31935e64f402.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

![](https://cdn.hashnode.com/res/hashnode/image/upload/v1697005727237/3ca06773-53f6-434e-a405-d6665a95e525.png)

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

![](https://cdn.hashnode.com/res/hashnode/image/upload/v1697005728591/344f95e7-9f90-4f1e-bc46-467644de585b.png)

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

![](https://cdn.hashnode.com/res/hashnode/image/upload/v1697005729917/15dff83a-5b7e-4be2-a03a-13c702b276b0.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.

![](https://cdn.hashnode.com/res/hashnode/image/upload/v1697005732491/7370d731-13b5-4bcc-8825-e0bddbd90411.png)

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

![](https://cdn.hashnode.com/res/hashnode/image/upload/v1697005734596/99fd82c9-721d-4ed5-bf4e-0f96a2c89f01.png)

![](https://cdn.hashnode.com/res/hashnode/image/upload/v1697005736094/8ddf6a15-8f21-49f6-b4af-b0ee06cfa38a.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, were using our Simple Javascript web application elestio example repository, so you can see in the above images that all of our fields are auto-filled.\*

Refer to these links to learn how to create our own [**_elestio.yml_**](https://docs.elest.io/books/cicd-pipelines/page/create-your-own-template-elestioyml?ref=blog.elest.io) for the project.

A sample elestio.yml for our deploying Simple Javascript web application is shown below. check it out on [**_github_**](https://github.com/elestio-examples/static/blob/main/elestio.yml?ref=blog.elest.io)

```
config:
  runTime: "static"
  version: ""
  framework: ""
  buildCommand: ""
  buildDir: ""
  runCommand: ""
ports:
  - protocol: "HTTPS"
    targetProtocol: "HTTP"
    listeningPort: "443"
    targetPort: "3000"
    targetIP: "172.17.0.1"
    public: true
    path: "/"
    isAuth: false
    login: ""
    password: ""
exposedPorts:
  - protocol: "HTTP"
    hostPort: "3000"
    containerPort: "80"
    interface: "172.17.0.1"

```

#### Step 6:

Click the **_Create CI/CD pipeline_** button to deploy your pipeline.

![](https://cdn.hashnode.com/res/hashnode/image/upload/v1697005738350/fac2f1c0-7b88-4df0-a8ec-8590a8dfe019.png)

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

![](https://cdn.hashnode.com/res/hashnode/image/upload/v1697005740773/70df27dd-8c7c-451a-80d7-1d1d222c1a2c.png)

![](https://cdn.hashnode.com/res/hashnode/image/upload/v1697005743189/362aa492-de3f-477e-800f-05830a80d519.gif)

You can now view your deployed URL and access your application by going to desired application pipeline details.

Please let us know by contacting our support [**_email_**](mailto:support@elest.io) or [**_ticketing_**](https://dash.elest.io/support/creation?ref=blog.elest.io) system if you give it a shot and encounter any problems or if anything goes wrong.

Join us on [**_discord_**](https://discord.gg/4T4JGaMYrD?ref=blog.elest.io) to know more.

_Originally published at_ [_https://blog.elest.io_](https://blog.elest.io/deploy-examples-apps-on-elestio-using-the-import-third-party-git-repository-feature/) _on November 21, 2022._