feat: Migrate to Neon DB and enhance connection status #1
Conversation
- Migrate from Azure PostgreSQL to Neon free tier - Add separate backend and database connection indicators - Show real-time status for both API and database - Improve connection monitoring with detailed health checks - Update DATABASE_URL configuration for Neon Fixes: Azure free credits expired, causing database timeout Benefits: Free Neon PostgreSQL with better reliability
There was a problem hiding this comment.
Pull request overview
This PR migrates the database from Azure PostgreSQL to Neon free tier and enhances the connection status UI to separately display backend API and database health in real-time. The changes resolve Azure credit expiration issues while improving visibility into system health through dedicated indicators for both services.
Key Changes:
- Split connection status indicator into separate backend (API) and database (DB) status displays
- Updated health check logic to parse and display individual status for backend and database
- Refactored CSS to support dual-indicator layout with vertical flex direction
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| frontend/styles.css | Refactored connection status styles to support two-row layout with separate styling for backend and database indicators |
| frontend/index.html | Updated HTML structure to include separate connection items for API and DB status |
| frontend/app.js | Modified updateConnectionStatus function signature and all call sites to handle separate backend/database status, updated health check to parse database status from API response |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| let isBackendConnected = false; | ||
|
|
||
| function updateConnectionStatus(status, message) { | ||
| function updateConnectionStatus(backendStatus, databaseStatus, backendMessage, databaseMessage) { |
There was a problem hiding this comment.
The backendMessage and databaseMessage parameters are defined but never used in the function body. These parameters should either be removed if not needed, or utilized to provide more detailed status information (e.g., in tooltips or for logging purposes).
| if (backendStatus === 'connected' && databaseStatus === 'connected') { | ||
| setTimeout(() => { | ||
| if (isBackendConnected && statusEl) { | ||
| statusEl.classList.add('hidden'); | ||
| } | ||
| }, 5000); |
There was a problem hiding this comment.
Potential race condition: Multiple calls to updateConnectionStatus can trigger multiple setTimeout callbacks that will all attempt to hide the status element after 5 seconds. If the status changes rapidly (e.g., connected -> disconnected -> connected), the later setTimeout could hide the status even when it should be visible due to a disconnection. Consider clearing previous timeouts before setting a new one using a module-level timeout ID.
Fixes: Azure free credits expired, causing database timeout
Benefits: Free Neon PostgreSQL with better reliability