Migration/docker postgres

[TVW96]

Summary & Changes 📃

• Resolves: Containerize Application with Docker #158

Summary

This PR introduces a Docker-based local development environment that standardizes the application’s infrastructure and workflow. The docker work flow establishes a consistent local development foundation by containerizing the application and routing traffic through a reverse proxy, consolidating the frontend and backend into a single, predictable local entry point.

Replacing the previous multi-port frontend-backend configuration, the application now runs entirely on http://localhost (port 80).

Resolving Issue

The monorepo exhibited cascading failures driven by unclear dependency boundaries and tooling conflicts, resulting in unstable builds and repeated troubleshooting.

This PR resolves dependency boundary and tooling conflict issues by removing the deduplicated and hoisted dependencies and allocating these to their correct execution environments before containerization. The result of these changes is a stable and maintainable development setup that aligns with production-ready deployment patterns.

Note

Follow-up work will continue with securely allocating environment variables into designated password files and compose.yaml configurations.

---

What is the expected behavior?

With these changes in place, developers should be able to spin up the full application locally using a consistent, repeatable workflow. The environment mirrors production-ready patterns while remaining focused on local development, enabling smoother onboarding and preparing the codebase for future cloud deployment work.

---

Relevant technical details

• http://localhost/ → Next.js frontend
• http://localhost/api → NestJS backend
• http://localhost:8080 → Traefik dashboard
• http://localhost:5050 or http://db.localhost → pgAdmin

---

Changes

• Dependency allocation has been normalized across environments
• Application has been containerized using Docker Compose
• Backend and frontend are routed through Traefik reverse proxy on port 80

---

How to Test 🧪

Steps to Reproduce

1. Run the setup script:
   • setup-macos-linux.sh or setup-windows.bat
2. Install dependencies from the project root:

   npm install

3. Run the docker container

   npm run docker:watch

[beimnettes]

I checked this branch locally and reviewed the changes.

The Docker setup and project structure look correct, and the application starts until required environment variables (such as JWT_SECRET) are needed. Those errors are expected locally and match the PR notes.

However, the CI checks are still failing and the branch is out of date with main. These issues should be resolved before merge.

[github-actions]

✅ Full E2E Test Results

Running full test suite (critical files changed)

Status	Count
✅ Passed	0
❌ Failed	0
📊 Total	0

View detailed report