Issue: Remove PGAdmin Service from Docker Compose

[TVW96]

Description

The pgadmin service is no longer required and should be removed from the Docker Compose configuration. It was initially included to provide a shared space for monitoring database updates. However, with the planned migration to Supabase, this functionality will be handled externally, making the local PGAdmin instance redundant.

Removing this service will:

Eliminate duplicate tooling
Simplify the development environment
Improve Docker Compose startup and teardown performance

Expected Action:
The application stack should start and run normally without the pgadmin service, with no impact to database connectivity or developer workflows.

Tasks

Remove the pgadmin service from the application and eliminate any dependencies or references to it across the codebase.

This task is not limited to deleting the service from the Docker Compose file—it also includes cleaning up any configuration, environment variables, scripts, or documentation that reference or rely on PGAdmin.

Scope of Work:

• Remove the pgadmin service from all Docker Compose files (e.g., compose.yaml, compose.test.yaml)
• Delete any PGAdmin-related environment variables or .env entries
• Remove exposed ports, volumes, and network references tied to PGAdmin
• Update or remove any scripts, configs, or documentation that mention or depend on PGAdmin
• Ensure no remaining service dependencies (depends_on, links, etc.) reference PGAdmin

Acceptance Criteria:

• The application builds and runs successfully without PGAdmin
• No broken references or unused configurations related to PGAdmin remain
• Docker Compose startup is successful and faster without the removed service
• Database connectivity and workflows remain fully functional without PGAdmin

Visual Aids

Expand ⬇️