Deploying

Deploying

Click Deploy Web Service to trigger a deployment. Each deploy runs three steps:

1. Build image: clones your repository and builds the container image. Skipped when the source is an existing image.
2. Deploy app: applies the new container configuration to your project.
3. Health check: waits for the new container to start serving traffic.

If any step fails, the deployment is marked failed and the previous version keeps serving traffic.

Build and deploy logs

The Deployments tab streams build output as it runs and keeps the full log for every past deployment.

Logs

The Logs tab streams the live output of your running container (stdout/stderr). This is separate from the build and deploy logs: here you see what your application prints while it runs. New lines appear live, and you can choose how many recent lines to load up front.

Runtime metrics

Live runtime metrics (CPU, memory, replicas) live on the Monitoring tab. It updates every 30 seconds when auto-refresh is on.

Redeploying

Push a new commit to the tracked branch, then trigger a redeploy from the Deployments tab. Each redeploy gets a fresh build and, on success, rolls out without dropping traffic.

Undeploying

If you don't need a service for a while, you can undeploy it. The running container is removed, but your configuration and persistent volumes are kept. You can redeploy the service at any time without losing your data.

To remove a service entirely, delete it from Settings instead — that also removes the volumes, and with them the data.