NavEd now stays online during brief infrastructure hiccups — even when the database is momentarily unreachable.
Occasionally, our hosting provider performs brief maintenance on the database connection layer. When this happened, every page — including the system health check that tells our servers "yes, NavEd is still running" — would fail. This could cause our hosting platform to mistakenly think NavEd had crashed and restart it unnecessarily, extending the downtime.
We've restructured how NavEd handles these brief interruptions. The health check now responds independently, so even during a momentary database blip, your servers stay running and recover instantly once the connection is restored. We also eliminated unnecessary database lookups when loading stylesheets, icons, and other static files — so those assets load faster and aren't affected by database hiccups at all.
Fixes and Improvements¶
- Health check endpoint now survives database proxy outages without triggering unnecessary server restarts
- Static files (CSS, JavaScript, images) no longer require a database connection to load
- Added structured logging to help us detect and diagnose infrastructure outages faster