Docs Your first deploy
Your first deploy
Create a project
A project groups the parts of one product: its apps, databases and services. Open Projects, choose New project and give it a name. Each project starts with a production environment, and you can add others such as staging.
Connect your repository
- In the environment, choose New resource, then Public repository for open code, or Private repository for your own.
- For a private repository on GitHub, create a GitHub App from Dekota under Sources › GitHub, then install it on the repositories it may read. Each Dekota console registers its own app. For other providers, add a deploy key.
- Pick the repository and the branch to deploy.
Choose how it is built
Dekota detects common languages and frameworks and builds them without any setup. If your repository has a Dockerfile, choose Dockerfile to use it exactly. For a folder of HTML, choose Static.
Check the port your app listens on. Most frameworks use 3000 or 8080. Add a health check path, such as /health, so a new version only goes live when it answers.
Add environment variables
Under Environment variables, add what your app reads at start. Mark values the build needs as build-time. Values stay on your server and are hidden in the console after you save them.
Deploy
Choose Deploy. The build log streams in the console. When it finishes you get a temporary address; the next guide puts the app on your own domain.
From now on, each push to the branch builds and deploys a new version. To deploy from your CI instead, copy the deploy hook URL from the app's settings and call it at the end of your pipeline.