This docker compose file uses these containers
- Postgres v13.1 as PostgreSQL DB https://hub.docker.com/_/postgres
- PgAdmin4 v4.28 as web based administration tool for the PostgreSQL database https://hub.docker.com/r/dpage/pgadmin4
- Caddy v2.2.1 as reverse proxy server https://hub.docker.com/_/caddy
To deploy, create an .env file in the same directory with docker-compose.yml file at server with your environment variables in it.
POSTGRES_LISTEN_IP=your-server-local-or-public-ip
POSTGRES_PASSWORD=your-secure-db-password
POSTGRES_SERVER_PORT=5432
PGADMIN_DEFAULT_EMAIL=your-web-admin-email
PGADMIN_DEFAULT_PASSWORD=your-secure-admin-password
PGADMIN_LISTEN_PORT=8080
CADDY_SITE_ADDRESS=:80
Caddy config is named Caddyfile and it is pretty straightforward.
Default configuration is
{$CADDY_SITE_ADDRESS} {
reverse_proxy pgadmin4:8080
}
which publishes PgAdmin web interface on the server's port 80 which is defined in .env file above.
Replace :80 with your domain name to get automatic https via LetsEncrypt. Add your domain to serve only https (recommended)
Don't forget to set your DNS first as Caddy automatically validates and creates certificates for you as soon as it started.
Allow 443/tcp port to outside access before rebuilding your docker-compose. This might be tricky as docker modifies iptables on linux directly https://docs.docker.com/network/iptables/
If you don't want to open your web interface to the public, you could always create a tunnel for it
sudo ssh -N -L 443:127.0.0.1:443 root@server-public-ip -i ~/.ssh/id_rsa
and visit https://127.0.0.1 after your docker containers up.
// Spin up the containers
# docker-compose up -d
// List active containers
# docker ps
// See the logs
# docker logs your_container_name
// Restart all in the compose file
# docker-compose restart
// Restart an individual container
# docker restart your_container_name