Deploy examples & apps on Elestio using the "Import Third-Party Git Repository" feature
What is the Import Third-Party Git Repository?
A feature of Elestio's 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 else's 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.
If you're new, sign up for Elestio, otherwise, login to your existing account.
Deploy Any Public repository Apps to the cloud using the CI/CD Import Third-Party Git Repository feature.
Go to CI/CD from the left sidebar.
Now, select the deployment source.
In this tutorial, I'm deploying using GITHUB, but you can also use GITLAB if you want to deploy your repository there.
Click the Import a Third-Party Git Repository
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.
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.
Choose Deployment Targets
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 Provider
- Select Service Cloud Region
- Select Service Plan
- Now Customize the target name and project (where the CICD Target will be created).
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.
Configure your Project
You can configure the project details by filling up the project name, branch, run time, version, framework, and root directory.
You can configure your project install, run, and build commands in the Build and output setting.
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.
You can list all of your project's API keys and secrets here if they were saved in ENV
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.
Refer to these links to learn how to create our own elestio.yml for the project.
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"
Click the Create CI/CD pipeline button to deploy your pipeline.
In a couple of moments, your application was successfully deployed on elestio 🚀.
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 or ticketing system if you give it a shot and encounter any problems or if anything goes wrong.
Join us on discord to know more.