Tenkai
Sign inStart for free
Skip to guide
Help center

Deploy your first application

Deploy your first web application on Tenkai from a public container image, configure its runtime port and check the HTTPS route.

Before you start

You need a team and a cluster whose setup has succeeded. Your applications run on your own servers. Start with projects, environments and clusters if you have not prepared a server yet.

This guide deploys the public image traefik/whoami:v1.11.0, which returns a small diagnostic page. For your own images, choose a server architecture they support.

Create a project

  1. Open Projects and choose Add project….
  2. Give it a name, such as hello-tenkai.
  3. If your team has several usable clusters, choose the Production cluster.
  4. Create the project. Its production environment comes with it.
Add project dialog with the name hello-tenkai.Add project dialog with the name hello-tenkai.
Example form with one usable cluster, so no cluster selector is needed.

Add a web application

  1. In the project, choose Add resource, then Application.
  2. Name it hello and choose Web application.
  3. Choose Container image as the build source and enter traefik/whoami:v1.11.0.
  4. Set Port to 80, the port whoami listens on.
  5. Choose Add application, then open the new resource.
Add application dialog with hello, web application and the public whoami image.Add application dialog with hello, web application and the public whoami image.
Example values for the public whoami image.

To deploy from Git or a Dockerfile instead, see Choose an application source.

Runtime port

Tenkai sends the requests of a web application to its Port, and checks that port answers during each deployment. Its HTTP server must listen on 0.0.0.0 at that port, not just localhost. A Dockerfile's EXPOSE instruction does not change it. See variables and the runtime port.

Deploy and check the route

  1. Choose Deploy on the resource. If the deployment fails, read its Details.
  2. Once the release is active, open the default route shown on the resource.
  3. If the browser does not load it over HTTPS yet, wait until the Domains tab shows its certificate as Active. Tenkai requests it once the application is deployed.
Application overview showing deploy, the default route and no active release before the first deployment.Application overview showing deploy, the default route and no active release before the first deployment.
The overview before the first deployment.

If the application is active but the URL fails, see troubleshooting.

Next steps

Deploy your own Node.js application, then connect a custom domain, or install a ready-made app such as Umami. Health shows what needs attention.

Files written inside a web application's container are lost at the next deployment. For uploads or database files, keep a directory or use a managed service.