Your first deploy

Šis turinys dar neišverstas į lietuvių kalbą.

This walks from a new account to a running service. Everything happens in the console.

Before you start

You need two things:

An account. Sign up at console.debesis.dev.
A container image. If you do not have one yet, read Coming from a VM first — it explains what an image is in terms of the install steps you already run.

1. Organisation, project, environment

Debesis nests three levels, and the shape matters more than it first appears:

Organisation — your company. Billing and members live here.
Project — the isolation boundary: quotas, cost, and access are all counted per project. Draw it wherever it belongs — per application, per team, or per customer.
Environment — a stage of that project’s app, such as production or staging. Services live inside an environment.

Create all three before you create anything else. A service always belongs to an environment, so there is nowhere to put one until this exists.

2. Get your image into the registry

Your image needs somewhere to live that the platform can pull from. Debesis includes a private Container Registry, under Registry → Images in the console.

You can also deploy from an external registry: the Compute wizard accepts image credentials for a registry you already use.

3. Create a Compute service

Go to Compute → Create. The wizard has four steps.

Basics

Name and describe the service. The name is what you will see in listings and logs, so something like api-gateway beats service-1.

Container

The substantive step:

Image and tag — what to run.
Image credentials — only if pulling from a private external registry.
Port — the port your application listens on inside the container.
Exposed externally — whether the service should take traffic from the internet.
Internet egress — whether the container may make outbound connections.
Health probes — a readiness path and a liveness path, for example /healthz and /ready. The platform uses these to decide whether an instance is healthy; give it real endpoints rather than leaving it guessing.
Resources — CPU and memory.
Autoscaling — optional, with a minimum and maximum replica count.
Volumes — mount Storage where the app expects a data directory.
Command and arguments — override the image’s default entrypoint if you need to.

Variables and secrets

Plain configuration goes in as environment variables. Anything sensitive — database passwords, API keys — goes in as a Secret instead, and is injected at runtime rather than stored in the service definition.

Review

Check it, then deploy.

4. Confirm it is running

Logs — collected per service, in the console under Logs.
Rollout status — the service page shows whether the new revision came up.

5. Do it again for the next app

Create a project, create an environment, point a service at the same image with different configuration. The tenth app should take about as long as the first — that is the whole point of the model.

If you get stuck

Mail founders@debesis.dev. The team is small enough that you get a person, not a ticket queue.