DeployVeraDocs

TECHNICAL REFERENCE

Deploy your first application

From a Git repository to a running API or website.

Last reviewed: Markdown

Prepare the repository

Connect GitHub or GitLab, or use a public HTTPS repository. Gitea is visible only for accounts whose connector DeployVera has enabled; it is not part of the general self-service flow.

Choose the branch, Dockerfile or automatic build method, and listening port. Bind the HTTP server to 0.0.0.0; a process listening only on localhost cannot be reached by the application proxy.

Create it in the panel

  • Select an active service and check its available application slots.
  • Choose the repository and branch. Automatic deployment follows pushes to that connected branch.
  • Configure the build method, port and required environment variables.
  • Start deployment, inspect build logs, then verify runtime status.

Python API example

Set the application port to 8000 for this example. Change the module path to match your project.

FROM python:3.13-slim
WORKDIR /app
COPY requirements.txt .
RUN pip install --no-cache-dir -r requirements.txt
COPY . .
CMD ["uvicorn", "app.main:app", "--host", "0.0.0.0", "--port", "8000"]

Verify the live revision

Runtime state and commit freshness are separate. Compare the live SHA with the head of the connected branch. A failed or cancelled build does not make the previous running version a deployment of the new commit. If a build fails, see /docs/en/build-errors for causes and fixes.

When the Node.js version is too old (Nixpacks)

With the automatic (Nixpacks) build, NIXPACKS_NODE_VERSION=22 selects only the major version; the minor version comes from the nixpkgs archive Nixpacks uses, and its Node.js 22 is 22.11.0. When a tool such as Astro needs Node.js 22.12 or newer, the build stops with Node.js v22.11.0 is not supported.

Fix: add a nixpacks.toml at the repository root and pin the nixpkgs archive to a newer commit. The commit below provides Node.js 22.13.1. Pinning an archive changes the whole package set of that commit, not only Node.js, so check the first build. The alternative for an exact version is the Dockerfile build method.

[phases.setup]
nixpkgsArchive = '51ad838b03a05b1de6f9f2a0fffecee64a9788ee'

Make later builds faster

To shorten build times, order the Dockerfile layers, add a .dockerignore and use package caches. Details are in /docs/en/faster-builds.