Deploy your app directly from a git repository and enjoy native continuous deployment on Koyeb.
The easiest way to deploy your apps on Koyeb is to connect the git repository containing your source code and let Koyeb manage the rest.
When using git-driven deployment, each time you push or merge your changes to your production branch, we build your application with all the required dependencies and deploy it in production. You natively benefit from continuous deployments with a completely automated build and deployment process.
This document explains how to deploy an application from a GitHub repository on Koyeb and is composed of two steps:
Koyeb provides the notion of Apps, which contain all the components needed to run your applications, including the ability to run one or more Services per App. Services can be deployed from a git repository or using a container image. You can read more about Koyeb Apps in the Apps Overview documentation.
When you deploy a Service on Koyeb, you have a few customizable settings. All settings can be transparently upgraded after the initial creation.
On the Koyeb control panel, click the Create App button. In the Deployment method section, select GitHub. During your first deployment, you are redirected to GitHub to:
Once this step is completed, you are redirected to Koyeb. You can now select the repository which contains your app and the branch which should be deployed.
We currently require a
Procfile to know how to launch your application.
Simply add a file a the root of your repository with the command needed to
execute your service in production prefixed by
web: yarn start
To learn more about how the language and build system is detected, please refer to this documentation.
To dive deeper, read about the Services Options.
Once your Service is deployed, you are redirected to the service page and can access your application:
You will see all the individual nodes, their regions, and their status depending on your configuration. Nodes might be detected as unhealthy due to a configuration issue.
If your deployment is failing, check the logs panel and refer to our troubleshooting deployments guide.