Local Dev Stack – PostgreSQL + Dragonfly + pgAdmin + RedisInsight

This repo provides a simple, reproducible local development stack:

• PostgreSQL 18 – main relational database
• Dragonfly – Redis-compatible in-memory datastore
• pgAdmin 4 – web UI for PostgreSQL
• RedisInsight – web UI for Dragonfly / Redis-compatible data

Services run with persistent volumes.

Fedora Silverblue / Podman setup

This repo is Podman-friendly and is the preferred setup for Fedora Silverblue.

Requirements:

• Podman
• podman-compose
• Rootless Podman socket enabled

Recommended setup:

systemctl --user enable --now podman.socket
python3 -m venv ~/.local/share/podman-compose-venv
~/.local/share/podman-compose-venv/bin/python -m pip install --upgrade pip
~/.local/share/podman-compose-venv/bin/python -m pip install podman-compose
ln -sf ~/.local/share/podman-compose-venv/bin/podman-compose ~/.local/bin/podman-compose

The Makefile defaults to:

COMPOSE ?= podman-compose
CONTAINER ?= podman

Docker setup

Docker is also supported by overriding the Makefile variables:

make up COMPOSE="docker compose" CONTAINER=docker

Setup

Copy the example environment file:

cp env-example .env

Edit .env if you want different ports, usernames, passwords, or database names.

Start the stack

make up

Show running services:

make ps

Tail all logs:

make logs

Stop services while keeping volumes:

make down

Stop services and remove volumes:

make down-v

make down-v deletes local database and Dragonfly data.

Service URLs

• pgAdmin: http://localhost:5050
• RedisInsight: http://localhost:5540
• PostgreSQL: localhost:5432
• Dragonfly: localhost:6379

Convenience commands

Open psql inside the Postgres container:

make psql

Open redis-cli inside the Dragonfly container:

make redis-cli

Tail individual service logs:

make logs-postgres
make logs-dragonfly
make logs-pgadmin
make logs-redisinsight

Default services

Service	Container	Port
PostgreSQL	dev-postgres	5432
Dragonfly	dev-dragonfly	6379
pgAdmin	dev-pgadmin	5050
RedisInsight	dev-redisinsight	5540

Notes

• Images are fully qualified so Podman does not prompt for registry selection.
• .env is ignored by Git.
• Persistent data lives in Podman/Docker named volumes.