Getting started
Deployments
Everything about how Lofenta builds, launches, and routes traffic to your app.
Lifecycle
A deployment moves through the following phases in order. Any failure stops progression and marks the deployment failed.
Deployment is waiting for a free build runner. Queue time is typically under 5 seconds.
Runner clones your repository at the exact commit SHA that triggered the build.
Dependencies are installed. Previous layer cache is restored if the lockfile has not changed.
Your build command runs (e.g. npm run build). Build output is streamed to the log.
The Docker container is launched. Your process must bind to the $PORT environment variable.
Lofenta polls your app for up to 60 seconds. On success, traffic switches to the new container.
The deployment is serving traffic. The previous container is gracefully shut down.
Something went wrong. Check the deployment log to see which phase failed and why.
A newer deployment started before this one finished. The build was stopped early.
Triggering a deployment
There are two ways to deploy:
Push to GitHub or GitLab
Every push to the branch configured for your project automatically queues a new deployment. If a deployment is already in progress, it is cancelled and replaced by the newer one.
Manual redeploy
Click Redeploy on the project page. This builds the latest commit on the tracked branch, which is useful for picking up config or environment variable changes without a code push. To redeploy a specific older commit, use Rollback instead.
Health checks
Before a new deployment goes live, Lofenta polls it to confirm it started successfully. The check succeeds when your app responds with any HTTP status below 500 on the configured port.
$PORT environment variable. Lofenta injects this automatically. Hardcoding port 3000 or 8080 will work during builds but may fail health checks in some configurations.Zero-downtime deploys
Traffic only switches to a new deployment after health checks pass. The old container keeps serving requests until the new one is ready. If the new deployment fails health checks, the old container stays live and no traffic is dropped.
Deployment history
The project page shows the last 20 deployments with their status, commit message, commit SHA, duration, and timestamp. The latest deployment's build log streams live on the project page; older logs are kept per your plan's retention window.
The Deployments dashboard section aggregates all deployments across all your projects.
Build cancellation
When a new push arrives while a build is running, Lofenta cancels the in-progress build and immediately starts a new one for the latest commit. This prevents old builds from deploying on top of newer code.
Next
Environment variables
Inject secrets and config