Step Snap 1 [Create Network & Create Dockers for PGAdmin/Postgres]:

docker network create pg-network

docker run -it \
-e POSTGRES_USER="root" \
-e POSTGRES_PASSWORD="root" \
-e POSTGRES_DB="ny_taxi" \
-v /ny_taxi_postgres_data:/var/lib/postgresql/data \
-p 5432:5432 \
--network=pg-network \
--name pg-database \
postgres:13

docker run -it \
-e [PGADMIN_DEFAULT_EMAIL="[email protected]](mailto:PGADMIN_DEFAULT_EMAIL=%[email protected])" \
-e PGADMIN_DEFAULT_PASSWORD="root" \
-p 8080:80 \
--network=pg-network \
--name pg-admin \
dpage/pgadmin4

The Basic Configuration for the Database and Data Visualization docker setting up within one network, but good to comprehend the details when we use further in the future:

1. Docker Network (pg-network)

   • Custom network creation enables containers to communicate using container names
   • Better and more flexible than using IP addresses
   • Makes container orchestration easier

2. Data Persistence (Volume mounting)

   -v /ny_taxi_postgres_data:/var/lib/postgresql/data
   
   

   • Data persists even if container is removed
   • Stored in host machine's /ny_taxi_postgres_data directory
   • Can reuse data when recreating containers

3. Port Mapping

   PostgreSQL: -p 5432:5432
   pgAdmin: -p 8080:80
   
   

   • Left is host port, right is container port
   • Access services from host machine:
     • PostgreSQL via localhost:5432
     • pgAdmin via localhost:8080

4. Environment Variables

   -e POSTGRES_USER="root"
   -e POSTGRES_PASSWORD="root"
   -e POSTGRES_DB="ny_taxi"
   
   

   • Using environment variables for configuration
   • More secure and flexible than hardcoding
   • Should use stronger passwords in production

5. Image Version

   postgres:13
   
   

   • Specific PostgreSQL version
   • Good practice to avoid unexpected issues from updates

Would you like me to explain any of these points in more detail?