Deploy an app

Compute is in preview. The v1alpha APIs can change, and Datum reviews Compute access requests manually.

Before you begin

Create a Datum Cloud account, an organization, and a project. For more information, see Account setup.
Install datumctl. For more information, see Install.
Run datumctl login. For more information, see Logging in.
Run datumctl plugin install compute. For more information, see Using plugins.
Select the project to deploy in with datumctl ctx use ORG_ID/PROJECT_ID. To confirm your account and project, run datumctl whoami. For more information, see Contexts and scoping.
Make sure that Compute access is active for the project. Run datumctl compute access and check that the Status line shows Active. If it doesn’t, see Request Compute access.

Deploy draw.io

This page deploys draw.io, an open source diagramming app, using the official docker.io/jgraph/drawio image with the general-purpose runtime class, which runs standard container images without changes. The app fits in one Instance (1 vCPU and 2 GiB of memory), stores nothing on the Instance, and needs no passwords or config files.

Deploy draw.io

To deploy draw.io to Dallas (us-central-1) and publish it on a public URL, run the following command:

datumctl compute deploy drawio \
  --image=docker.io/jgraph/drawio:31.4.6 \
  --runtime-class=general-purpose \
  --location=us-central-1 \
  --http-port=8080

The flags do the following:

--image: the container image to run, pinned to a draw.io release. Compute requires the registry host in the image reference, such as docker.io.
--runtime-class=general-purpose: runs the image as a standard container in a lightweight virtual machine. Without this flag, Datum uses the unikernel class, which needs a specially packaged image. To compare the two, see Choose a runtime class.
--location=us-central-1: runs one Instance in Dallas.
--http-port=8080: attaches an ALB to the workload and publishes port 8080, where draw.io serves HTTP.

The command asks you two questions:

The first time you deploy in a project, it asks whether to create a network named default. Enter y.
It prints a plan and asks Apply? (Y/n). Enter y.

The command then creates the workload, waits for the Instance to start, and publishes the URL. The end of the output is similar to the following:

Rollout complete in 22s.

Publishing...
  Backends     1 healthy across us-central-1
  Edge         programmed
  Certificate  issued

  https://peril-oven-p53hn.datumproxy.net

The last line is the hostname of the ALB attached to the workload. Your hostname is different. The command also saves the workload definition to workload.yaml in the current directory.

Check that draw.io is available

To list the workloads in your project, run the following command:

datumctl compute workloads

Continue when HEALTH is Available and READY is 1/1. The URL column shows the ALB hostname from the deploy output.

Open draw.io and draw a diagram

In your web browser, go to the URL from the deploy output. Datum’s ALB serves draw.io over HTTPS, and the app opens a blank diagram. If the browser can’t find the site, wait a minute and try again.Click the rectangle in the General shape panel, double-click it, and type Hello from Datum. To keep it, click File > Export as > PNG….The editor runs in your browser, so your diagrams stay with you even when Datum restarts or replaces the Instance.

Optional: See the Instance

To list the workload’s Instances, run the following command:

datumctl compute instances --workload=drawio

The INTERNAL IP column shows the Instance’s private IPv6 address on the default gVPC network. The Instance has no public address, so traffic from the internet reaches draw.io only through the ALB.

Clean up

To delete the draw.io workload, its Instance, and its ALB, run the following command and enter y to confirm:
datumctl compute destroy drawio
Delete workload.yaml from the current directory.
Optional: If this tutorial created the default network and no other workload uses it, delete the network:
datumctl delete network default

What’s next

To deploy your own image, check that your app listens on IPv6 and serves plain HTTP. During the preview, Instances have no persistent disks and no readiness checks. For details, see Compute limitations.
To pass configuration and secrets to a workload, see Compute configuration.
To package your own app as a fast-starting unikernel, see Unikernels.
To run in more locations or with more Instances, see Placement and scaling.
To learn how Datum’s control plane turns your resources into running Instances, DNS, and load balancers, see Platform API.

Introduction

Explore

Before you begin

Deploy draw.io

Clean up

What’s next

​Before you begin

​Deploy draw.io

​Clean up

​What’s next

Before you begin

Deploy draw.io

Clean up

What’s next