You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: bootcamp/materials/1-dimensional-data-modeling/README.md
+10-1Lines changed: 10 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -53,7 +53,7 @@ There are two methods to get Postgres running locally.
53
53
3. Set up DataGrip, DBeaver, or your VS Code extension to point at your locally running Postgres instance.
54
54
4. Have fun querying!
55
55
56
-
### 🐳 **Option 2: Run Postgres in Docker**
56
+
### 🐳 **Option 2: Run Postgres and PGAdmin in Docker**
57
57
58
58
- Install Docker Desktop from **[here](https://www.docker.com/products/docker-desktop/)**.
59
59
- Copy **`example.env`** to **`.env`**:
@@ -79,6 +79,15 @@ There are two methods to get Postgres running locally.
79
79
- You can check that your Docker Compose stack is running by either:
80
80
- Going into Docker Desktop: you should see an entry there with a drop-down for each of the containers running in your Docker Compose stack.
81
81
- Running **`docker ps -a`** and looking for the containers with the name **`postgres`**.
82
+
- If you navigate to **`http://localhost:5050`** you will be able to see the PGAdmin instance up and running and should be able to connect to the following server:
83
+

84
+
Where:
85
+
- Host name: host.docker.internal
86
+
- Port: 5432
87
+
- Username: postgres
88
+
- Password: postgres
89
+
90
+
82
91
- When you're finished with your Postgres instance, you can stop the Docker Compose containers with:
0 commit comments