App Platform

How it works#

You connect a repository once. From then on a push is the deploy: we fetch the commit, detect the framework, build it into a container image on an isolated build machine, start it, and route your app’s address to it. If the build fails, nothing changes — the previous version keeps serving and the deployment is marked failed with the reason.

Each app gets an address of the form https://v2-<app-name>.ahurasense.com straight away, with a certificate. You can add your own domains alongside it.

Deploy your first app#

1. Open Apps in the dashboard and connect GitHub, GitLab or Bitbucket. This happens once, in the provider’s own consent screen.
2. Choose New app, pick a repository and branch, and create it. The first deployment starts immediately.
3. If the app needs environment variables to build or run, add them under Environment, then deploy again. See Environment variables.
4. Push a commit. It builds and goes live on its own.

git push origin main

Ways to integrate#

There are four ways to start a deployment. All of them produce the same kind of deployment, with the same build, logs and rollback.

Creating an app is an API call too, so a whole environment can be stood up from a script. An API key acts as the person who created it and can do exactly what they can do in the dashboard — no more.

Two steps always happen outside any API, here and on every similar platform: connecting your git account, which runs through the provider’s own consent screen, and adding DNS records for a custom domain, which you do wherever your domain’s DNS is hosted.

Next#