Add local PostgreSQL development environment with Docker

[Copilot]

Implements local PostgreSQL database setup for development, replacing reliance on remote Heroku database.

Core Changes

• Docker Compose: PostgreSQL 14 Alpine with health checks, persistent volumes, default credentials studybuddy/studybuddy
• Environment management: Added dotenv package, .env.example with sensible defaults
• Database connection logic: Conditional SSL based on proper hostname parsing instead of substring matching

  // Before: vulnerable substring check
  const isProduction = databaseUrl.includes('amazonaws.com');
  
  // After: proper URL parsing
  const url = new URL(databaseUrl);
  isProduction = url.hostname.endsWith('.amazonaws.com');

Documentation

• SETUP.md: Quick start guide, Docker commands, troubleshooting, project structure
• README.md: Links to local development setup

Usage

docker compose up -d
npm run seed
npm run start:dev

Fixes CodeQL alert js/incomplete-url-substring-sanitization by validating hostname properly.

Original prompt

Go ahead and implement option 1, with the postgresql database running locally.

The user has attached the following files from their workspace:

• package.json

[Chronological Review: The conversation began with the user returning to their project after a long break, expressing a desire to analyze the app and reassess the database situation. The user proposed implementing existing seed commands/data to ensure their development environment has access to a database, either locally or through Docker. The user then confirmed their intention to run a PostgreSQL database locally. The most recent command was the user's request to implement this option.]

[Intent Mapping:

1. "I want to get back to this project." - User's intent to resume work on the project.
2. "I think I would propose starting by analyzing the app, reassessing the db situation..." - User's request to analyze the app and database.
3. "Go ahead and implement option 1, with the postgresql database running locally." - User's explicit command to set up a local PostgreSQL database.]

[Technical Inventory:

• PostgreSQL: The user intends to run this database locally.
• Docker: Mentioned as an alternative for database setup.
• npm: User plans to perform a significant update after reassessing the stack.]

[Code Archaeology:

• The user is currently working with the package.json file located at /workspaces/studybuddy/package.json. This file is crucial for managing project dependencies and scripts.]

[Progress Assessment:

• Completed: User has confirmed the intention to run PostgreSQL locally.
• Pending: Implementation of the local PostgreSQL database and any necessary seed commands/data.]

[Context Validation: All critical information for continuation is captured, including the user's intent to set up a local database and the specific file being worked on.]

[Recent Commands Analysis:

• Last Agent Commands: The user requested to implement the local PostgreSQL database setup.
• Tool Results Summary: No specific tool results were returned as the command was a user request.
• Pre-Summary State: The agent was actively preparing to implement the user's request for a local PostgreSQL database setup when the token budget was exceeded.
• Operation Context: The user's commands are directly related to their goal of getting the project back up and running with a functional database.]

1. Conversation Overview: - Primary Objectives: - "I want to get back to this project." - "I think I would propose starting by analyzing the app, reassessing the db situation..." - "Go ahead and implement option 1, with the postgresql database running locally." - Session Context: The user is returning to a project after a long break, focusing on setting up a local PostgreSQL database and ensuring their development environment is ready. - User Intent Evolution: The user initially sought to analyze the app and database situation, then confirmed their choice to implement a local PostgreSQL database.

2. Technical Foundation:

• PostgreSQL: The user intends to run this database locally.
• Docker: Mentioned as an alternative for database setup.
• npm: User plans to perform a significant update after reassessing the stack.

3. Codebase Status:

• File Name: package.json
• Purpose: Manages project dependencies and scripts.
• Current State: The user is currently reviewing this file to ensure proper configuration for local database connectivity.
• Key Code Segments: Not specified in the recent context.
• Dependencies: This file is crucial for the overall project setup.

4. Problem Resolution:

• Issues Encountered: None specified yet.
• Solutions Implemented: User's decision to run PostgreSQL locally is a proactive step.
• Debugging Context: No ongoing troubleshooting efforts mentioned.
• Lessons Learned: User is reassessing their stack and database setup.

5. Progress Tracking:

• Completed Tasks: User has confirmed the intention to run PostgreSQL locally.
• Partially Complete Work: Implementation of the local PostgreSQL database is pending.

6. Active Work State:

• Current Focus: Implementing a local PostgreSQL database.
• Recent Context: User has requested to implement the local PostgreSQL database setup.
• Working Code: The package.json file is being reviewed.
• Immediate Context: User is preparing to set up a local database for development.

7. Recent Operations:

• Last Agent Commands: User requested to implement the local PostgreSQL database setup.
• Tool Results Summary: No specific tool results were returned as the command was a user request.
• Pre-Summary State: The agent was actively preparing to implement the user's request for a local PostgreSQL database setup.
• Operation Context: The user's commands are directly related to their goal of getting the project back up and running with a functional database.

8. Continuation Plan:

• Pending Task 1: Implement the local PostgreSQL database setup.
• Pending Task 2: Review and implement ex...

Created from VS Code via the GitHub Pull Request extension.

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[tymonaghan]

@copilot I get an empty response from the app after I start and seed the db via docker and do npm run build and npm start, Can you double check this and also add a VS Code launch config.json with launch configs that allow me to start the db connection via docker and run my app each with a simple debug script i can play through the VS Code debug tab?