Guides
Deployments & Rollbacks
Understand the deployment lifecycle, build logs, and how to roll back.
Deployment lifecycle
git push → webhook → clone → detect framework → build image → start container → healthy ✓
Each step is logged in real time and visible in the Deployments tab.
Deployment statuses
| Status | Meaning |
|---|---|
pending | Queued, waiting to start |
building | Docker image is being built |
running | Container is live and serving traffic |
failed | Build or startup failed — check logs |
stopped | Manually stopped |
Live build logs
Click View logs on any active deployment to open the live log stream. Logs are streamed via Server-Sent Events (SSE) and display in real time.
Past deployment logs are stored and can be viewed at any time.
Rolling back
To roll back to a previous deployment:
- Go to Project → Deployments tab.
- Find the deployment you want to restore.
- Click Rollback.
LoomDeploy will:
- Stop the current running container
- Start the previously-built image for that deployment
- Update the Traefik routing to point at the restored container
Rollbacks are instant because the Docker image is already built — no rebuild is needed.
Framework auto-detection
When no Dockerfile is found, LoomDeploy detects your framework and generates one:
| Framework | Detected by |
|---|---|
| Node.js | package.json |
| Python | requirements.txt / Pipfile |
| Go | go.mod |
| PHP | composer.json |
| Ruby | Gemfile |
| Java (Maven) | pom.xml |
| Java (Gradle) | build.gradle |
You can always override auto-detection by committing your own Dockerfile to the repository root.