Deploy and configure
Ready-to-run files that set up a server and the apps on it.
Between knowing what a stack needs and having it running there are files to write: a Compose file for the apps, an environment file for their settings and a bootstrap file for the server itself. The tools here generate them from templates built on official sources.
They write files; they don't deploy. You read the result, fill in your own secrets and run it on a server you control. Defaults are private: nothing is published to the internet unless you choose a proxy.
A path through this category
- Start from a Spec
Bring the Deployment Spec from the sizing step, or choose the apps again.
- Generate the app files
Create docker-compose.yml and .env.example for the stack, with the exposure mode you want.
- Prepare the server
Create a cloud-init file for a new server: user, SSH keys, firewall and Docker, with the Compose files written in place.
Tools in this category
- Docker Compose GeneratorReady-to-run Compose files for self-hosted apps, from source-backed templates. You run them on your own server.Open the tool
- cloud-init Generator for Ubuntu 24.04A bootstrap file for a new Ubuntu Server 24.04 LTS, to paste into the user-data field when you create the server. It prepares the server; it doesn't deploy anything.Open the tool
- docker run to Docker Compose converterPaste a docker run command and get the same container as a Compose service, checked by the Compose Analyzer. Nothing is run, and nothing leaves this page.Open the tool
- Docker Compose to docker run converterPaste a Compose file, pick a service, and get the docker run command that starts the same container. Your file stays in this browser.Open the tool
- Docker Compose to Kubernetes converterPaste a Compose file and get Kubernetes manifests, with a gap report of everything that has no equivalent. Your file stays in this browser, and no secret value is copied.Open the tool
- Reverse proxy config generator: Caddy, Traefik and nginxList your sites, or read them from a Compose file, and get the configuration for Caddy, Traefik or nginx: HTTPS with Let's Encrypt, HTTP redirected to HTTPS and basic security headers. Everything stays in this browser, and a password never goes in: basic auth takes a hash only.Open the tool
- Dockerfile generatorChoose a runtime and get a multi-stage Dockerfile and a .dockerignore that run as a non-root user, pin their base images and cache dependencies, with every line explained. The Dockerfile Linter checks the result right here.Open the tool
- SSH config generator and key helperDescribe each server once, then connect with ssh and a short name: the right user, port and key, a jump through a bastion, and SSH tunnels to services that listen only on the server. Make the key with ssh-keygen on your computer, or, if you choose, in this browser. Nothing leaves this page.Open the tool
- systemd service generatorFill in how your program runs and get a .service file that systemd reads as written, with the install commands and an explanation of every field. Everything is written in your browser.Open the tool
- cron to systemd timer converterPaste a cron schedule or a whole crontab line. You get what it means, when it runs next, and a systemd service and timer that do the same, with the commands that install them.Open the tool
- Docker daemon.json generatorChoose the settings and get a daemon.json that dockerd accepts, an explanation of every key and the commands that put it in place safely. Everything is written in your browser.Open the tool
Background: Self-hosted apps