From git push to a live address. No server to set up.
Connect a GitHub repository: every push to the tracked branch starts a build, your tests run, then the new version replaces the old one without downtime.
At a glance
- Source
- GitHub repository or Docker image
- Build
- Auto build or Dockerfile
- Tests before release
- Up to 10 checks
- Rollback
- No rebuild
A deployment, step by step.
01
A push to the tracked branch.
A service is created from a GitHub repository: you pick the branch to track (main by default) and the application's port.
From then on, every commit pushed to that branch starts a build. Automatic deployment can be turned off per service, to freeze an environment.
02
The stack is recognised.
The auto builder reads the repository and picks the recipe: Next.js, Nuxt, Astro, Vite, Node.js, Python, Go or PHP, with no configuration file.
A Dockerfile at the root takes over when you want control of the image. The build cache keeps what has not changed between builds.
03
Your tests, before release.
A kx712.yml file at the root of the repository declares up to 10 checks: tests, lint, one command each, in the image of your choice.
The first failure stops everything. Nothing is deployed and the live version stays in place.
04
No downtime.
The new version starts next to the old one. Traffic only moves once it is ready, then the old one stops.
Every build's logs stay available, even weeks later.
05
Production, staging, development.
The environment is chosen when the service is created, and each one has its own address.
Staging and development stay behind a token: you send the link to your client, they review before release.
06
Back to the previous version.
Every successful deployment keeps its image in the registry. A rollback redeploys it as is, with no rebuild.
Current environment variables apply: they do not go back to their state at the time.
07
From the terminal or the editor.
The CLI lists your services, redeploys, follows logs and rolls back. Install it with bun add -g Webgune.
The VS Code extension deploys the service linked to the open repository and shows build logs without leaving the editor.
What it does not do yet.
Deploy-on-push works through GitHub. A Docker image is redeployed from the dashboard, the CLI or the VS Code extension.
kx712.yml looks like GitHub Actions without being compatible. For heavy tests or a version matrix, keep your usual CI.
Node builds run with npm. A bun.lock, pnpm-lock.yaml or yarn.lock is set aside and dependencies are resolved again.
A rollback does not restore the environment variables of the time.
Questions about deployment
The rest of the platform
Your first deployment, tonight.
Connect a repository, pick the branch: the build starts on its own.