Deploy your application

This walkthrough starts with a Spring Boot repository and ends with a public URL. deliberate. deploys container images; the build remains under your control and can run locally or in your existing CI.

Before you start

You need:

• a deliberate. account and Team;
• Docker, Podman, or nerdctl; and
• a Java application that listens on a known HTTP port.

The example uses Java 21, Maven Wrapper, port 8080, and Spring Boot Actuator’s /actuator/health endpoint. Change those details to match your application.

1. Package the Java application

Add a Dockerfile at the repository root:

FROM eclipse-temurin:21-jdk AS build
WORKDIR /src
COPY . .
RUN ./mvnw -DskipTests package \
 && cp "$(find target -maxdepth 1 -name '*.jar' ! -name '*-plain.jar' | head -1)" /app.jar

FROM eclipse-temurin:21-jre
RUN useradd --system --uid 10001 app
COPY --from=build --chown=10001:10001 /app.jar /app.jar
USER 10001
EXPOSE 8080
ENTRYPOINT ["java", "-jar", "/app.jar"]

For Gradle, replace the Maven build command with ./gradlew bootJar and copy the resulting application JAR from build/libs/.

2. Install the CLI and select your Team

curl -fsSL https://get.deliberate.cloud | sh
deliberate login
deliberate team list
deliberate team use <team-slug>

team use makes the selection persistent for later registry and deployment commands.

3. Push the image to the deliberate. registry

Let the CLI mint a short-lived push credential and log your local container runtime in:

deliberate registry login

Docker is auto-detected first; use --runtime podman or --runtime nerdctl to choose another runtime. The command prints the registry and Team-scoped image prefix. Tag and push an immutable version:

docker build -t registry.deliberate.cloud/<team-slug>/hello-java:1.0.0 .
docker push registry.deliberate.cloud/<team-slug>/hello-java:1.0.0

Your Team’s workloads receive pull access to its private registry namespace automatically.

4. Describe the deployment

Create .deliberate/project.yaml:

team: <team-slug>
project: hello-java
flow: default

Create .deliberate/app.yaml:

resource: component
name: app
image: registry.deliberate.cloud/acme/hello-java:1.0.0
cpu: 0.5
memory: 1Gi
ports:
  - port: 8080
    protocol: http
healthcheck:
  path: /actuator/health
  port: 8080
  initialDelay: 30s

---
resource: route
host: hello-java
visibility: public
rules:
  - path: /
    to: app
open:
  - label: Open hello-java
    path: /
    description: Open the deployed application.

Replace acme with your Team slug. The component declares runtime resources and its internal port. The separate route is the deliberate public exposure. If your app has no Actuator endpoint, point healthcheck.path at another endpoint that returns HTTP 2xx when the process is ready.

5. Apply and open

Run these commands from the directory containing .deliberate/:

deliberate apply --env production
deliberate open --env production

apply validates the complete tree and streams progress until the application is ready. open opens the public route declared above.

6. Deploy and test a change

Before changing production, deploy the complete Project into a temporary Environment. Change the image tag in .deliberate/app.yaml, then apply to any name matching the default Flow’s preview-* stage:

deliberate apply --env preview-new-greeting
deliberate open --env preview-new-greeting

There is no separate create step. On its first apply, deliberate. recognises the preview-* name and forks the current production Environment according to the Flow’s clone policy. Components, configuration, routes, secrets, and supported data resources come across together; the changed .deliberate/ tree is then reconciled on top. The preview receives its own generated routes, so it can be exercised without replacing production.

When the change is accepted, keep the same desired state and apply it to production:

deliberate apply --env production

Then remove the temporary Environment and everything it stood up:

deliberate envs delete preview-new-greeting

Environment deletion is idempotent, making the same cleanup command suitable for a local workflow or CI.

7. If it does not become ready

deliberate components list --env production
deliberate deployments list --env production
deliberate logs --env production --component app

The usual first-deploy failures are a wrong image path, the process listening on a different port, or a health endpoint that is absent or not ready yet. The Environment canvas in the console shows the same component, route, rollout, and health state.