Updating your application
Edit a running app or deploy new code.
There are two ways to update a running application: the Edit drawer for in-place changes, and a new deployment when you want to ship new code.
Editing a running app
The Edit drawer is the fastest way to update most settings without a full redeploy. Open it by clicking Edit on the app detail page.
What you can edit
- Environment variables
- CPU and memory allocation
- Number of replicas
- Application port
- Health check path and enabled/disabled toggle
Update times
| Change | What happens | Time |
|---|---|---|
| Environment variable | Triggers a full rebuild and redeploy | ~5-15 min |
| CPU, memory, or replicas | Updates the running deployment without a rebuild | ~2-3 min |
| Port | Updates the ingress routing rule | ~30 s |
| Health check | Updates the probe configuration | ~30 s |
Redeploying with new code
When you want to deploy a new commit:
- Go to Applications and click on your app.
- Click Redeploy.
- In the Source step, select the new commit you want to deploy.
- Adjust build configuration and resources if needed.
- Click Deploy.
The new deployment builds and replaces the existing one. The old deployment is marked as superseded.
Build cache behavior
When redeploying, the Reuse Existing Build option is enabled by default. If the same repository, commit, and build method combination has been built before, the cached image is used immediately -- skipping the build phase entirely.
To force a fresh build (e.g., if dependencies have changed without a code change), toggle off Reuse Existing Build.