What happens on every push?
Zenifra receives the configured-branch webhook, runs the build and deployment flow, and shows logs and status in the console.
Deployment
Push-based deployment to production
Connect GitHub, validate the build, and follow logs on every push to the main branch, with Node.js and Python as the initial runtimes.
From commit to an observed deployment
The GitHub flow puts builds, webhooks, branches, and logs in one visual path so your team can understand the state of every release.
Currently supported runtimes
Start with Node.js and Python, the runtimes currently available for automated deployment. Zenifra handles the build and publishing so your team can focus on application code.
Connect your GitHub account in the console
Choose the organization, repository, and main branch
Select a currently supported runtime: Node.js or Python
Configure environment variables and the HTTP port
Follow the build, webhook, logs, and deployment status
Current limitations
Automated deployment follows the branch configured in the console and depends on GitHub webhooks. For projects outside Node.js and Python, use Docker/OCI image deployment while new runtimes are added.
When to use GitHub deployment
The ideal path for teams that already work by branch and want less friction between commit, build, and production.
When to use GitHub deployment
Use it when the team wants to publish on every push without maintaining a pipeline, server, or manual script.
Node.js and Python APIs
The flow supports projects using currently supported runtimes, with builds and logs in the console.
Small teams
Reduces operational setup for squads that need to go from commit to production quickly.
How the flow works
From repository authorization to the status observed in the console after every release.
01
Connect GitHub
Authorize access and choose the organization, repository, and main branch.
02
Configure the build
Set the runtime, command, environment variables, and application HTTP port.
03
Observe every push
Follow the build, webhook, logs, and deployment status in the console.
Build settings
Before enabling automated deployment, confirm the details that define how your application starts.
Build settings
Confirm the runtime, build/start command, and variables before enabling automated deployment.
Main branch
The configured branch defines which pushes enter the publishing flow.
Application port
Zenifra needs to know which HTTP port the process exposes.
Docker fallback
Projects outside the current runtimes can use Docker/OCI deployment.
The real console flow
Authorize GitHub, choose the repository, confirm the main branch, and publish. On every push, follow the build, logs, and deployment status in the same console.
- Connect GitHub and authorize repository access
- Select the organization, repository, and main branch
- Choose Node.js or Python runtime
- Define the command, environment variables, and HTTP port
- Validate the build, webhook, and logs in the console
GitHub connection
The connection screen should show the organization, repository, branch, and runtime before automated deployment is enabled.
Frequently asked questions
Short answers to understand push deployment before connecting your repository.
Which runtimes are available?
The initial flow focuses on Node.js and Python. For other runtimes, use Docker/OCI while the platform expands support.