Fix FAQ formatting: remove extra blank lines, replace images with text, split entries

- Remove extra blank lines in code blocks (8c9b0fdaa5, 05aad03ef3,
  b459de9135, 89733da275, a32ed35da6, 7c97a61529)
- Add proper indentation in SQL/YAML/bash code blocks (7df3102580,
  30622af850, 30dcc71db8, 7f7aa5f5e6)
- Replace images with text descriptions (af2b85f346, 5d66421473,
  4ae927f8a0)
- Remove missing image references (52858dfd98)
- Split inline Q&As from aeaede4fd1 into separate FAQ files

Author: alexeygrigorev

_questions/data-engineering-zoomcamp/module-1/025_30dcc71db8_postgres-docker-volume-backup-restore.md

@@ -4,30 +4,50 @@ question: How can I back up and restore PostgreSQL data stored in a Docker volum
 sort_order: 25
 ---
 
-- Method 1: Docker volume backup
-  ```bash
-  # List Docker volumes
-  docker volume ls
-  # Backup while the container is running
-  docker run --rm \
-  -v ny_taxi_postgres_data:/data \
-  -v $(pwd):/backup \
-  ubuntu tar czf /backup/postgres_backup.tar.gz /data
-  # Restore
-  docker run --rm \
-  -v ny_taxi_postgres_data:/data \
-  -v $(pwd):/backup \
-  ubuntu tar xzf /backup/postgres_backup.tar.gz -C /
-  ```
-- Method 2: Using pg_dump
-  ```bash
-  # Backup
-  docker exec -t postgres_container pg_dump -U root -d ny_taxi > ny_taxi_backup.sql
-  # Restore
-  docker exec -i postgres_container psql -U root -d ny_taxi < ny_taxi_backup.sql
-  ```
-- Method 3: Copying the host directory
-  ```bash
-  # When using a host-mounted directory in docker-compose.yaml
-  cp -r ./ny_taxi_postgres_data ./ny_taxi_postgres_data_backup
-  ```
+### Method 1: Docker volume backup
+
+List Docker volumes:
+
+```bash
+docker volume ls
+```
+
+Backup while the container is running:
+
+```bash
+docker run --rm \
+    -v ny_taxi_postgres_data:/data \
+    -v $(pwd):/backup \
+    ubuntu tar czf /backup/postgres_backup.tar.gz /data
+```
+
+Restore:
+
+```bash
+docker run --rm \
+    -v ny_taxi_postgres_data:/data \
+    -v $(pwd):/backup \
+    ubuntu tar xzf /backup/postgres_backup.tar.gz -C /
+```
+
+### Method 2: Using `pg_dump`
+
+Backup:
+
+```bash
+docker exec -t postgres_container pg_dump -U root -d ny_taxi > ny_taxi_backup.sql
+```
+
+Restore:
+
+```bash
+docker exec -i postgres_container psql -U root -d ny_taxi < ny_taxi_backup.sql
+```
+
+### Method 3: Copying the host directory
+
+When using a host-mounted directory in `docker-compose.yaml`:
+
+```bash
+cp -r ./ny_taxi_postgres_data ./ny_taxi_postgres_data_backup
+```

_questions/data-engineering-zoomcamp/module-1/060_30622af850_ingest-pipeline-setup.md

@@ -5,65 +5,78 @@ question: How do I ensure that the ingestion pipeline runs successfully and in w
 sort_order: 60
 ---
 
-Step 1: Create a common network
-Ensure that you have created a common network (`pg-network`). This is to ensure that you run several containers in the same network so that they can communicate with each other.
-Pg-network is the broader network layer on top of which you will run -
-1. Postgres container,
-2. the Dockerized script container (the container which you will have your ingestion script)
-3. pgadmin container
-Command:
+### Step 1: Create a common network
+
+Ensure that you have created a common network (`pg-network`). This allows several containers to communicate with each other. On top of this network you will run:
+
+1. Postgres container
+2. The Dockerized ingestion script container
+3. pgAdmin container
+
 ```bash
 docker network create pg-network
 ```
 
-Step 2: Run the Postgres container
-Once you’ve created the network, start running each container one-by-one.  First, run the Postgres container
+### Step 2: Run the Postgres container
+
+Once you’ve created the network, start running each container one by one. First, run the Postgres container:
+
 ```bash
 docker run -it \
--e POSTGRES_USER="root" \
--e POSTGRES_PASSWORD="root" \
--e POSTGRES_DB="ny_taxi" \
--v ny_taxi_postgres_data:/var/lib/postgresql \
--p 5432:5432 \
---network=pg-network \
---name pgdatabase \
-postgres:16
+    -e POSTGRES_USER="root" \
+    -e POSTGRES_PASSWORD="root" \
+    -e POSTGRES_DB="ny_taxi" \
+    -v ny_taxi_postgres_data:/var/lib/postgresql \
+    -p 5432:5432 \
+    --network=pg-network \
+    --name pgdatabase \
+    postgres:16
 ```
-Remember, if `postgres:18` causes issues, use `postgres:16` as mentioned above
 
-Step 3: Build the docker container for the pipeline
-Ensure your current working directory is /pipeline. Then, run this command to build your container -
+If `postgres:18` causes issues, use `postgres:16` as shown above.
+
+### Step 3: Build the Docker container for the pipeline
+
+Ensure your current working directory is `/pipeline`, then build:
+
 ```bash
 docker build -t taxi_ingest:v001 .
 ```
 
-Step 4: Run the ingestion container
-Ensure your current working directory is /pipeline. Then, run this command to build your container -
+### Step 4: Run the ingestion container
+
 ```bash
 docker run -it \
---network=pg-network \
-taxi_ingest:v001 \
---pg_user=root \
---pg_pass=root \
---pg_host=pgdatabase \
---pg_port=5432 \
---pg_db=ny_taxi \
---year=2021 \
---month=1 \
---target_table=yellow_taxi_trips
+    --network=pg-network \
+    taxi_ingest:v001 \
+    --pg_user=root \
+    --pg_pass=root \
+    --pg_host=pgdatabase \
+    --pg_port=5432 \
+    --pg_db=ny_taxi \
+    --year=2021 \
+    --month=1 \
+    --target_table=yellow_taxi_trips
 ```
-Make sure that you use the parameters in the command exactly same as what you have in your script. For example, if your script as the click parameter `–pg_user` then use `pg_user`, else if it is something like `--user` then change the above command to include `--user` instead of `--pg_user`
 
-Step 5 (Optional): To validate if your records reached the table
-To validate if your records really reached the Postgres table, run PGCLI using the following command -
+Make sure that you use the parameters in the command exactly as defined in your script. For example, if your script uses `--pg_user` then use `--pg_user`; if it uses `--user` then change the command accordingly.
+
+### Step 5 (Optional): Validate the ingested records
+
+To check if your records reached the Postgres table, run pgcli:
+
 ```bash
 uv run pgcli -h localhost -p 5432 -u root -d ny_taxi
 ```
-Once inside pgcli, run the following to get table names -
-```postgres
+
+List tables:
+
+```sql
 \dt
 ```
-Then, to validate how many rows have been ingested, run the following -
-```postgres
-SELECT COUNT(*) FROM yellow_taxi_trips
+
+Check row count:
+
+```sql
+SELECT COUNT(*) FROM yellow_taxi_trips;
 ```

_questions/data-engineering-zoomcamp/module-1/071_7f7aa5f5e6_pgcli-after-installing-pgcli-and-checking-with-pgc.md

@@ -7,67 +7,65 @@ sort_order: 71
 
 This error occurs because psycopg cannot find the PostgreSQL client library (libpq). The simplest solution with uv is to install the binary version of psycopg, which bundles the required library.
 
-Solution 1: Add psycopg-binary (Recommended)
-```
-uv add psycopg-binary
+**Solution 1:** Add psycopg-binary (Recommended)
 
+```bash
+uv add psycopg-binary
 uv run pgcli -h localhost -p 5432 -u root -d ny_taxi
 ```
 
-Solution 2: Manually edit pyproject.toml
-```
+**Solution 2:** Manually edit `pyproject.toml`
+
+```toml
 [project]
 dependencies = [
-"pgcli>=4.2.0",
-"psycopg-binary>=3.0.0",
+    "pgcli>=4.2.0",
+    "psycopg-binary>=3.0.0",
 ]
 ```
+
 Then sync your environment:
-```
+
+```bash
 uv sync
 ```
 
-Additional troubleshooting steps (not uv-specific) if the issue persists:
-
-1. Check Python Version:
+**Additional troubleshooting steps** (not uv-specific) if the issue persists:
 
-```
-$ python -V
-```
+1. Check Python version — ensure Python is at least 3.9:
 
-Ensure Python is at least 3.9. The 'psycopg2-binary' installation may fail on older versions.
+    ```bash
+    python -V
+    ```
 
-2. Environment Setup (if using a non-uv workflow):
+2. Environment setup (if using a non-uv workflow):
 
-```
-$ conda create --name de-zoomcamp python=3.9
-$ conda activate de-zoomcamp
-```
+    ```bash
+    conda create --name de-zoomcamp python=3.9
+    conda activate de-zoomcamp
+    ```
 
-3. Install Required Libraries:
+3. Install required libraries:
 
-```
-pip install psycopg2-binary
-pip install psycopg_binary
-```
+    ```bash
+    pip install psycopg2-binary
+    pip install psycopg_binary
+    ```
 
 4. Upgrade pgcli:
 
-```
-pip install --upgrade pgcli
-```
+    ```bash
+    pip install --upgrade pgcli
+    ```
 
 5. Install pgcli via Conda:
 
-```
-conda install -c conda-forge pgcli
-```
+    ```bash
+    conda install -c conda-forge pgcli
+    ```
 
-If you still encounter an error like
-```
-ModuleNotFoundError: No module named 'psycopg2'
-```
-then try:
-```
+If you still encounter `ModuleNotFoundError: No module named 'psycopg2'`, try:
+
+```bash
 pip install psycopg2-binary
 ```

_questions/data-engineering-zoomcamp/module-1/076_52858dfd98_postgres-modulenotfounderror-no-module-named-psyco.md

@@ -1,12 +1,5 @@
 ---
 id: 52858dfd98
-images:
-- description: 'image #1'
-  id: image_1
-  path: images/data-engineering-zoomcamp/image_b7e005cb.png
-- description: 'image #2'
-  id: image_2
-  path: images/data-engineering-zoomcamp/image_c56a8539.png
 question: 'Postgres - ModuleNotFoundError: No module named ''psycopg2'''
 sort_order: 76
 ---
@@ -17,10 +10,6 @@ Issue:
 ModuleNotFoundError: No module named 'psycopg2'
 ```
 
-<IMAGE:image_1>
-
-<IMAGE:image_2>
-
 Solution:
 
 1. Install psycopg2-binary:

_questions/data-engineering-zoomcamp/module-1/113_af2b85f346_gcp-gcloud-ms-vs-code-gcloud-auth-hangs.md

@@ -1,44 +1,34 @@
 ---
 id: af2b85f346
-images:
-- description: 'image #1'
-  id: image_1
-  path: images/data-engineering-zoomcamp/image_df9492cb.png
-- description: 'image #2'
-  id: image_2
-  path: images/data-engineering-zoomcamp/image_6b01ae01.png
-- description: 'image #3'
-  id: image_3
-  path: images/data-engineering-zoomcamp/image_bc858c4b.png
-- description: 'image #4'
-  id: image_4
-  path: images/data-engineering-zoomcamp/image_a231d54c.png
-- description: 'image #5'
-  id: image_5
-  path: images/data-engineering-zoomcamp/image_2f5bf08c.png
 question: GCP gcloud + MS VS Code - gcloud auth hangs
 sort_order: 113
 ---
 
-If you are using MS VS Code and running `gcloud` in WSL2, when you first try to login to GCP via the `gcloud` CLI with `gcloud auth application-default login`, you may encounter an issue where a message appears and nothing happens:
+If you are using MS VS Code and running `gcloud` in WSL2, when you first try to login to GCP via the `gcloud` CLI with `gcloud auth application-default login`, you may encounter an issue where the terminal prints a long OAuth URL and then shows a series of "not found" errors for browsers:
 
-<{IMAGE:image_1}>
+```
+Your browser has been opened to visit:
+    https://accounts.google.com/o/oauth2/auth?response_type=code&client_id=...
 
-There might be a prompt asking if you want to open it via a browser. If you click on it, it will open a page with an error message:
+/usr/bin/xdg-open: 882: x-www-browser: not found
+/usr/bin/xdg-open: 882: firefox: not found
+/usr/bin/xdg-open: 882: chromium: not found
+...
+xdg-open: no method available for opening '...'
+```
 
-<{IMAGE:image_2}>
+VS Code may show a notification: "Your application running on port 8085 is available" with an "Open in Browser" button. Clicking it may lead to an error page.
 
 **Solution:**
 
-- Hover over the long link.
-- `Ctrl + Click` the long link.
-- Click "Configure Trusted Domains here."
-- A popup will appear; pick the first or second entry.
-
-<{IMAGE:image_3}>
-
-<{IMAGE:image_4}>
-
-<{IMAGE:image_5}>
+1. Hover over the long OAuth URL in the terminal output.
+2. `Ctrl + Click` the link — VS Code will show a dialog: "Do you want Code to open the external website?" with buttons **Open**, **Copy**, **Configure Trusted Domains**, and **Cancel**.
+3. Click **Configure Trusted Domains**.
+4. A dropdown will appear with options like:
+   - "Trust https://accounts.google.com"
+   - "Trust google.com and all its subdomains"
+   - "Trust all domains (disables link protection)"
+   - "Manage Trusted Domains"
+5. Pick the first or second entry (e.g., "Trust https://accounts.google.com").
 
 Next time you run `gcloud auth`, the login page should pop up via the default browser without issues.

_questions/data-engineering-zoomcamp/module-2/011_0b468d3cc5_why-use-secrets-instead-of-embedding-json-key.md

@@ -0,0 +1,7 @@
+---
+id: 0b468d3cc5
+question: Why use secrets instead of embedding the JSON key in the Kestra task?
+sort_order: 11
+---
+
+Secrets prevent credential exposure and make workflows easier to manage.