Deployments
Running an application in an environment — the three routes (CODE, SaaS/ERP, managed service) and the common lifecycle.
A deployment is an application that runs in an environment, with its resources, its configuration and its network exposure. Not to be confused with the build, which produces the image beforehand (see Key concepts).
Three deployment routes
| Route | What for | Details |
|---|---|---|
| CODE | Your application, from your Git repository | Deploying a CODE app |
| SaaS / ERP | A pre-packaged application (Odoo, WordPress…) | SaaS / ERP applications |
| Managed service | A database or a middleware (PostgreSQL, Redis…) | Managed services |
All of them are deployed into an environment of a project and share the same lifecycle once online.
💡 Several services at once? If your application is made of several blocks that talk to each other (API + front end + worker + database), describe it in one go with NubiStack instead of deploying each service separately.
Common lifecycle
Whichever route you take, a deployed application can be:
- updated (resources, environment variables, image),
- restarted or synchronized,
- paused then resumed,
- rolled back to a previous version,
- deleted.
The details are in Deployment lifecycle.
Deployment states
| State | Meaning |
|---|---|
PENDING | Waiting to be picked up |
BUILDING | Image build in progress (CODE apps) |
DEPLOYED / RUNNING | Deployed and running |
HEALTHY | Healthy (health check OK) |
FAILED | Failed |
NubiImport (importing an image)
Import a Docker image from an external registry (Docker Hub, GHCR, GitLab) into Nubiecloud to deploy it.
Deploying an application from code
Every detail of deploying a CODE app — supported frameworks, resources, env variables and secrets, domain and TLS, health check, replicas and migrations.