SHIP YOUR CODE.
Understand how Boottify deploys your application — from a GitHub push through Docker build to a live K8s deployment with SSL.
DEPLOYMENT TRIGGERS
Deployments can be triggered in two ways:
GitHub Push
Push to your connected repository. The Boottify GitHub App receives a webhook and triggers an automatic deployment.
Deploy Wizard
Use the deploy wizard in the Control Center to create a new app. Select a template or repository, configure settings, and deploy.
BUILD PROCESS
Boottify builds your application into a Docker image on the server. The build process follows these steps:
Clone Repository
The latest code is pulled from your GitHub repository.
Docker Build
Your Dockerfile is used to build the application image. Environment variables are injected during the build.
Push to Registry
The built image is pushed to the local container registry for K8s to pull.
KUBERNETES PROVISIONING
A Kubernetes namespace is created (or updated) for your app with the following resources:
| Resource | Purpose |
|---|---|
| Deployment | Manages pod replicas running your Docker container |
| Service | Exposes your app within the cluster (ClusterIP) |
| Secret | Stores environment variables securely |
| Ingress | Routes external traffic via Traefik to your service |
DNS & SSL SETUP
After the K8s deployment is live, DNS records are created and an SSL certificate is provisioned automatically.
DNS Records
A subdomain (your-app.boottify.com) is created via the Hetzner DNS API. For custom domains, you point your A record to 95.216.3.90.
SSL Certificate
Let's Encrypt certificates are provisioned automatically. Nginx handles SSL termination and proxies traffic to the K8s service.