pgAdmin Manager

Manages the pgAdmin Docker container, providing a web UI for PostgreSQL database management.

Architecture

pgadmin-manager/
├── docker-compose.yml   # pgAdmin 4 container (pinned to 8.6)
└── run.sh               # lifecycle CLI

Connects to the shared nginx-proxy_net network and reaches PostgreSQL at codai_postgres:5432. Server configurations are persisted in a named volume (pgadmin_data).

Commands

./run.sh start    # start pgAdmin container
./run.sh stop     # stop container (config persists in volume)
./run.sh status   # show status and URL
./run.sh open     # print access URL

How to Execute Tasks

Start pgAdmin

Check your session context for the absolute script path, then run:

<plugin-root>/pgadmin-manager/run.sh start

Open http://localhost:8082 in a browser. Login: admin@codai.local / pgadmin.

To connect to PostgreSQL inside pgAdmin, add a server with:

• Host: codai_postgres
• Port: 5432
• User: codai / Password: pgpass

Check status

<plugin-root>/pgadmin-manager/run.sh status

Prerequisites

Start in this order:

1. proxy-manager start — creates the shared Docker network
2. postgres-manager start — PostgreSQL must be running before pgAdmin connects

Configuration

Rules

• Start postgres-manager before this plugin — pgAdmin cannot connect without PostgreSQL.
• Port 8082 is bound to 127.0.0.1 — accessible from the host only.
• Server configurations survive container restarts (stored in pgadmin_data volume).
• Use stop when done; the container uses restart: unless-stopped and survives reboots.
• Use docker compose down -v only when you intentionally want to delete saved server configs.

Related Plugins

• proxy-manager — creates the shared Docker network (start first)
• postgres-manager — PostgreSQL container that pgAdmin connects to