fix forking all branches

fix docker-compose, dockerignore

fix remove duplicated section

fix README.md

Author: egarciajulia

README.md

@@ -14,15 +14,17 @@ You've just joined a new team building a dashboard for visualizing financial tra
 
 ## Your Mission: A Three-PR Workflow
 
-**Important First Step:** Before you begin, please **fork this repository**. You will work entirely on your own fork, creating pull requests within that repository. **Do not create any pull requests to the original upstream repository.**
+**Important First Step:** Before you begin, please **fork this repository** (Make sure you fork all the branches, you will need them).
+
+You will work entirely on your own fork, creating pull requests within that repository. **Do not create any pull requests to the original upstream repository.**
 
 Your work will be organized into three separate pull requests within your own repository. We recommend following these steps in order.
 
 ### A Quick Glossary of Branches
 
 *   **`main`**: The initial state of the codebase. You will branch from here.
 *   **`fix-bug-666`**: A simulated PR from a junior developer. This branch contains their work for you to review.
-*   **`fix/haunted-codebase`**: The branch you will create from `main` to fix the existing technical debt (the N+1 and re-render bugs).
+*   **`fix/haunted-codebase`**: The branch you will create from `main` to fix the existing technical debt.
 *   **`feature/transaction-tags-grid`**: The branch you will create from `fix/haunted-codebase` for the new feature (database migration and data grid).
 
 
@@ -71,34 +73,6 @@ To address the display bug, I decided to handle filtering directly in the fronte
 I used AI tools for minor code refactoring and to generate some boilerplate for the frontend pagination component.
 ```
 
-### PR #1: The Code Review
-
-Your first task is to act as a mentor and review a "PR" from a junior developer.
-
-1.  **Understand the Context:** The junior dev's work is on the `fix-bug-666` branch. On that branch, read the `BUG-666.md` file to understand the original problem.
-2.  **Open the PR:** In your own repository, open a pull request from `fix-bug-666` to your `main` branch. Use the PR description template below.
-3.  **Perform the Review:** Go to the "Files Changed" tab of the PR you just created. Leave comments directly on the code, providing a mix of high-level architectural feedback and specific line-by-line notes.
-4.  **Abandon the PR:** Once your review is complete, **close the pull request without merging.**
-
-#### PR #1 Description Template
-```md
-### What I Did
-This PR fixes the transaction display bug by filtering transactions on the frontend to only show relevant entries. I've also implemented server-side pagination for better performance.
-
-### How to Test
-1. Checkout this branch.
-2. Run `docker-compose up --build`.
-3. Navigate to the frontend at `http://localhost:3000`.
-4. Observe that only relevant transactions are displayed.
-5. Verify that pagination controls are now active and functional.
-
-### Architectural Decision Record (ADR)
-To address the display bug, I decided to handle filtering directly in the frontend component. This approach simplifies the backend and leverages the client's processing power for a snappier user experience. For pagination, I added a new `GET` parameter `page` and `page_size` to the existing `/api/v1/transactions/` endpoint, and updated the frontend to send these parameters.
-
-### AI Usage Summary
-I used AI tools for minor code refactoring and to generate some boilerplate for the frontend pagination component.
-```
-
 ### PR #2: Fixing Technical Debt
 
 Now, it's time to fix the *other* bugs lurking in the `main` branch.
@@ -134,7 +108,7 @@ With the codebase stabilized, you can now build the new feature. This PR will be
 The final deliverable is **a link to your forked repository.** When you submit it, we expect to see the following:
 
 *   **PR #1 (Code Review):** A **closed** pull request from `fix-bug-666` to `main`, containing your review comments.
-*   **PR #2 (Bug Fixes):** An **open** pull request from `fix/haunted-codebase` to `main`, containing the fixes for the N+1 and re-render bugs.
+*   **PR #2 (Bug Fixes):** An **open** pull request from `fix/haunted-codebase` to `main`, containing the fixes.
 *   **PR #3 (New Feature):** An **open** pull request from `feature/transaction-tags-grid` to `main`, containing the database migration and the new data grid feature. This PR will implicitly include the commits from PR #2 as its base.
 
 ### PR Description Template for PRs #2 and #3

docker-compose.yml

@@ -0,0 +1,44 @@
+services:
+  db:
+    image: postgres:18.1
+    volumes:
+      - postgres_data:/var/lib/postgresql/data/
+    environment:
+      POSTGRES_DB: ${DB_NAME}
+      POSTGRES_USER: ${DB_USER}
+      POSTGRES_PASSWORD: ${DB_PASSWORD}
+      PGDATA: /var/lib/postgresql/data/pg18
+    ports:
+      - "5432:5432"
+    healthcheck:
+      test: ["CMD-SHELL", "pg_isready -U ${DB_USER} -d ${DB_NAME}"]
+      interval: 5s
+      timeout: 5s
+      retries: 5
+
+  backend:
+    build: ./backend
+    command: bash -c "python /app/seed.py && uvicorn app.main:app --host 0.0.0.0 --port 8000"
+    volumes:
+      - ./backend:/app
+    ports:
+      - "8000:8000"
+    environment:
+      DATABASE_URL: postgresql://${DB_USER}:${DB_PASSWORD}@db:5432/${DB_NAME}
+      SECRET_KEY: ${SECRET_KEY}
+    depends_on:
+      db:
+        condition: service_healthy
+
+  frontend:
+    build: ./frontend
+    ports:
+      - "3000:3000"
+    volumes:
+      - ./frontend:/app
+      - /app/node_modules
+    depends_on:
+      - backend
+
+volumes:
+  postgres_data:

frontend/.dockerignore

@@ -0,0 +1,24 @@
+# Docker
+.dockerignore
+Dockerfile
+
+# Git
+.git
+.gitignore
+
+# Runtime
+node_modules
+build
+dist
+.env
+.env*.local
+
+# Logs
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*
+
+# IDEs
+.idea
+.vscode
+*.swp