Feature #261
Updated by Bricklou 19 days ago
The application is configured entirely through environment variables (database connection, authentication providers, email, security settings, etc.). Today, each setting is checked independently, so a missing or invalid environment variable can go unnoticed at startup and only surface later as a broken, unrelated feature. As an administrator, I want the application to validate all of check its environment variables configuration when it starts, starts and refuse to start fail immediately with a clear, specific error naming the problematic variable if one when something is missing or invalid — invalid, instead of starting successfully and failing silently somewhere else. falling back to a default or breaking later inside an unrelated feature. This check should cover apply consistently across every configurable subsystem consistently, (authentication providers, email, security, etc.), not just some of them.