Skip to content

Addis Ababa, Ethiopia. Support on 6993.MCP ready. Attach your agents 100% self-service. Sign up using google or phone number. No sales call to get started

System status
AletCloud

Deploying apps

Deploy an app

From a GitHub repository to a live HTTPS URL, then onto a domain of your own.

On this page

Deploy from GitHub

  1. 01In the console, open App hosting and choose Create app.
  2. 02Connect the GitHub account, then pick the repository and the branch.
  3. 03The stack is detected and a container image is built. Build logs stream while it runs.
  4. 04The app goes live over HTTPS on a free aletcloud subdomain.

From then on, every push to that branch builds and releases on its own.

Before the first deploy, check that the app reads the PORT environment variable and binds 0.0.0.0. How deploys work covers why that is the rule which decides whether a successful build turns into a running app.

Add a custom domain

Connecting a domain takes two steps, and the first changes nothing for visitors. Ownership has to be proven before the record that moves traffic is handed out, so nobody can attach a domain they do not control.

Step one, prove the domain is yours

Add the domain in the app’s settings. A TXT record is shown to create at the DNS provider. Create it, then press Check now.

dns
_alet-challenge.yourdomain.com.   TXT   "alet-domain-verification=<your token>"​

The exact name and token are in the console, so copy them from there rather than from this page. Nothing changes for visitors at this stage, and the record is safe to delete once verification succeeds.

Step two, point traffic here

Once ownership is proven, the console reveals the record that sends visitors to AletCloud: an A record pointing at the address in the settings panel. Add it when the site is ready to go live, because that is the moment traffic moves.

dns
yourdomain.com.       A       <address shown in your settings>​app.yourdomain.com.   A       <address shown in your settings>​

A naked domain has to use an A record, since the DNS standard does not let a CNAME sit alongside the records a zone apex needs. For a subdomain the console may offer a CNAME target instead. Use whichever record it shows.

DNS changes usually spread in under an hour. There is no need to keep pressing Check now: unverified domains are re-checked every ten minutes, and the certificate is issued as soon as DNS resolves.

TLS certificates are issued and renewed automatically for every app subdomain and every verified custom domain. There is nothing to buy, install or rotate.

If a domain shows as drifted

Drifted means a domain that used to point here no longer resolves here. The app and its settings are untouched. Restoring the record reconnects it on its own, with no second verification. If Cloudflare or another CDN now sits in front of the site, drifted is expected and nothing is broken.

Support is free, and a person answers.

Call 6993System statusContact