Skip to content
Ownkube

Deploy Spring Boot

Deploy a Spring Boot app on Ownkube in minutes. Push your repo and Ownkube builds it and ships it, and you get a live URL with automatic TLS. Managed Postgres, logs, metrics, and one-click rollbacks come built in. No cloud account to start.

What you’ll need

Section titled “What you’ll need”
  • A Spring Boot app in a GitHub or GitLab repository
  • About five minutes

Deploy it

Section titled “Deploy it”

  1. Connect your repo

    Sign in at app.ownkube.io/login, open Settings, and connect the GitHub App (or GitLab) so Ownkube can reach your repository. Already have a prebuilt image in a registry? Point Ownkube at it instead. See Registries.

  2. Create a Web deployment

    From your dashboard, choose Create deployment, pick Web, and select your Spring Boot repo. Ownkube builds it and pushes the image to a registry it manages for you.

  3. Set the port

    Spring Boot’s default port is 8080. Set that as the port so traffic routes to your app; SERVER_PORT overrides the default if you need a different one. You can change it later in Settings.

  4. Add environment variables

    Set SPRING_PROFILES_ACTIVE=prod and any datasource variables your app reads, such as SPRING_DATASOURCE_URL. Mark secrets with the Secret toggle. See Environment variables.

  5. Deploy

    Click Create deployment. The deployment page streams the build, then startup and health checks. When the status goes healthy, open the generated hostname on the Overview tab. Your Spring Boot app is live, with TLS included.

Notes for Spring Boot

Section titled “Notes for Spring Boot”

Executable jar

Spring Boot packages your app as a single executable jar, which Ownkube runs directly once the build finishes.

Port 8080 and SERVER_PORT

Spring Boot’s default port is 8080; SERVER_PORT overrides it. Set the port to whichever one your app actually listens on.

Spring profiles via env

Set SPRING_PROFILES_ACTIVE=prod so Spring Boot loads application-prod.properties (or .yml) instead of your local defaults.

Datasource to managed Postgres

Point SPRING_DATASOURCE_URL, SPRING_DATASOURCE_USERNAME, and SPRING_DATASOURCE_PASSWORD at the Postgres database you attach.

Bring your own Dockerfile

Want full control of the build? Add a Dockerfile to your repo and Ownkube uses it, reading the port from its EXPOSE line.

Add a database

Section titled “Add a database”

Need Postgres? Add a Database in one click and Ownkube injects the connection string as DATABASE_URL (plus PGHOST, PGUSER, and friends) into your app. Map the pieces into SPRING_DATASOURCE_URL, SPRING_DATASOURCE_USERNAME, and SPRING_DATASOURCE_PASSWORD. See Databases.

Scale and observe

Section titled “Scale and observe”

Once you’re running, turn on autoscaling on CPU and memory, watch logs and metrics on every deployment, and roll back a bad deploy in one click.

Databases Attach managed Postgres in one click and read DATABASE_URL.
Autoscaling Scale on CPU and memory thresholds automatically.