shamimgeek/docker-compose-postgres

Postgresql with pgadmin4 and docker-compose and practice sql

docker-compose-postgres-pgadmin4

Requirements:

• docker
• docker-compose

Quick Start

• Clone this repository
• Go to directory, cd docker-compose-postgres
• Run this command docker-compose -f docker-compose-postgres-pgadmin4.yml up -d

Environment Variables

• POSTGRES_USER the default value is postgres
• POSTGRES_PASSWORD the default value is passw0rd
• PGADMIN_PORT the default value is 8080
• PGADMIN_DEFAULT_EMAIL the default value is [email protected]
• PGADMIN_DEFAULT_PASSWORD the default value is passw0rd

Access to postgres:

• localhost:5432
• Username: postgres (as a default)
• Password: passw0rd (as a default)

Access to postgres using terminal:

docker exec -it postgres psql -U postgres

for more postgresql commands check here

Access to PgAdmin:

• URL: http://localhost:8080
• Username: [email protected] (as a default)
• Password: passw0rd (as a default)

Add a new server in PgAdmin:

• Host name/address postgres
• Port 5432
• Username as POSTGRES_USER, by default: postgres
• Password as POSTGRES_PASSWORD, by default passw0rd

docker-compose-postgres's Issues

Use docker-entrypoint-initdb.d

If we create a Dockerfile

FROM postgres:12.4-alpine
ADD /SQL/*.sql /docker-entrypoint-initdb.d/

and then use it in docker-compose-postgres-pgadmin4.yml:

version: '3.5'

services:
  postgres:
    container_name: postgres
    build: .

...
...

then it will automatically run those sql files for data setup.

What do you think?

If you would like to do additional initialization in an image derived from this one, add one or more *.sql, *.sql.gz, or *.sh scripts under /docker-entrypoint-initdb.d (creating the directory if necessary). After the entrypoint calls initdb to create the default postgres user and database, it will run any *.sql files, run any executable *.sh scripts, and source any non-executable *.sh scripts found in that directory to do further initialization before starting the service.

Warning: scripts in /docker-entrypoint-initdb.d are only run if you start the container with a data directory that is empty; any pre-existing database will be left untouched on container startup. One common problem is that if one of your /docker-entrypoint-initdb.d scripts fails (which will cause the entrypoint script to exit) and your orchestrator restarts the container with the already initialized data directory, it will not continue on with your scripts.