Why
The story behind Tent
If you do backend work, you know the drill. You need a database, maybe a cache, a message broker, a mail catcher. So you write a docker-compose file. Then another project needs different versions, so you write another one. Before long you have a graveyard of compose files, each slightly different, none of them quite right. Or worse, you're running services as system packages and they conflict with each other.
Compose files are great for defining application stacks, but they're overkill when all you want is a PostgreSQL instance to develop against. You shouldn't need to write a YAML file, pick an image, map ports, set environment variables, and figure out volumes just to get a database running locally.
Tent skips all of that. Type tent start postgres -d and you have a PostgreSQL instance running. Need Redis and Mongo too? tent start redis mongo -d. Want to run MySQL 5.7 alongside the latest on a different port? Just start it twice with different tags. Need to skip auth for quick local testing? Add --insecure. Want it to survive reboots? Add --restart always.
24 services, all pre-configured with sensible defaults. One binary, no runtime dependencies beyond Podman, no root access needed.