The part of a PaaS you use most should have the least power — so I built Mooring
Description and use
Mooring simplifies Docker app deployment on a VPS by auto‑generating Dockerfiles and compose files, securing the UI with a read‑only Docker socket proxy, and handling HTTPS and secrets automatically.
Problem
Deploying Dockerized side‑projects on cheap VPSes is tedious: each time you copy‑paste the same mistakes, you give the deployment tool too much privilege, and you risk exposing the Docker socket to root‑level access.
Outcome
Mooring simplifies Docker app deployment on a VPS by automating Dockerfile and compose generation, securing the deployment UI with read‑only socket access, managing HTTPS, and handling secrets safely, all while running as an unprivileged service.
Workflow
- Install Mooring as an unprivileged systemd service
- Connect a git repository to Mooring
- Create a mooring.yaml describing the app (language, ports, secrets)
- Click Deploy in the web UI to trigger deployment
Evidence
Mooring is a small, security‑first, self‑hosted control plane for Docker — a tiny PaaS.
The read plane never holds a read‑write Docker socket
Mooring generates and owns the compose file. You don't hand‑edit it.
- Record date: 2026-09-06T17:52:48.647Z