voodu
by ClowkSelf-hosted PaaS. One HCL file. One voodu apply.
Heroku-shaped deploys on your own boxes. The CLI streams the build over SSH: no commit, no push, no bare repo.
deployment "acme" "web" {
image = "ghcr.io/acme/web:latest"
replicas = 2
ports = ["8080"]
}
ingress "acme" "web" {
host = "acme.com"
service = "web"
tls {
enabled = true
provider = "letsencrypt"
email = "[email protected]"
}
}Install
curl -fsSL voodu.clowk.in/install | bashWhat you get
One HCL file
Manifests describe the running system: apps, ingress with TLS, and stateful services with backup.
Commitless deploys
voodu apply streams the build context to the server over SSH. No commit, no push, no bare repo.
Builds, ships, routes, swaps
One command builds the image, starts the new release, moves the traffic and stops the old one.
Plugins
Stateful services such as Postgres and Redis come as plugins, installed with the server.
Your own boxes
The installer sets up the CLI, the controller, Docker and a systemd unit on a Linux server.
Deploy on a tag
A Git tag can start a deploy, so the tag is the record of what is live.
Questions
Do I need Kubernetes?
No. voodu runs on a plain Linux server with Docker.
Do I have to commit before a deploy?
No. The CLI streams the build context straight to the server.
Which machines does it install on?
The server runs on Linux. On macOS the installer sets up the client only.