New: the AI Agent now understands any question
Documentation

Site from GitHub (Next.js, static, Node.js)

For sites with their own code, Voltzzflow builds and publishes your repository automatically.

Where can the code come from?

  • From GitHub: connect your GitHub account and pick the repository from the list, private repositories included. You decide which repositories it can access.
  • Public URL: the https address of a public repository on GitHub, GitLab, Bitbucket or Codeberg.
  • Write code: start from a simple template and write the code in the Voltzzflow editor, no GitHub account needed.

What goes in each field?

  • Branch: the branch to publish, usually main.
  • Base directory: the app's folder, if it is not at the repository root.
  • Install command: for example npm ci.
  • Build command: for example npm run build.
  • Publish directory: for static sites, the folder produced by the build, for example dist.
  • Start command and Port: for Node.js, for example npm start and the port your app listens on.
  • Notification webhook: optional, a Slack or Discord URL that gets a message on every deploy.

Advanced settings are optional. Leave them empty to use the defaults for the chosen type.

What happens after publishing?

Every deploy has a build log and a live site log. Each push to the chosen branch redeploys the site automatically. You can compare a deploy with the previous one and roll back to an older version.

Environment variables, databases and cron

On the site page you add environment variables (available at build and run time), separate databases reachable over the internal network, and cron jobs that run commands on a schedule. Changing a variable redeploys the site automatically.

Last updated

Read next