Deploy

Deployment

Zenifra publishes HTTP applications from two main sources: GitHub Repository or OCI image. This choice defines how the application is built, updated, and versioned.

Choose the right method

MethodDescriptionUpdate
GitHubZenifra uses the repository, branch, runtime, and commands defined during creationAutomatic when auto-deploy was enabled
OCI ImageZenifra runs an already built Docker/OCI imageManual by changing the image in the console or API

Use GitHub when the team wants to publish directly from source code and keep deployment connected to the main branch.

Use OCI image when the image is already generated by external CI, when you need to promote immutable tags, or when you want to control the artifact outside Zenifra.

Publication flow

  1. GitHub: select the repository and branch.
  2. OCI: provide the public or private image.
  3. Port: configure the port where the application listens.
  4. Variables: register secrets and configuration.
  5. Online: validate the application at *.clients.zenifra.com.

What to validate after deployment

  • the application responds on the public URL
  • build logs do not show errors
  • application logs appear in the console
  • CPU, RAM, storage, and HTTP requests appear according to plan
  • custom domain points to the correct destination, when configured
  • a new push only updates automatically when auto-deploy is enabled

Next steps

Checklist before production

Practical checklist to review deploy, configuration, security, database, observability, and billing before going live.

GitHub Deployment

Create a project from GitHub and use auto-deploy to update the instance automatically on push.

On this page

DeploymentChoose the right methodPublication flowWhat to validate after deploymentNext steps