Kubestro » Server

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 its environment variables when it starts, and refuse to start with a clear, specific error naming the problematic variable if one is missing or invalid — instead of starting successfully and failing silently somewhere else.

This check should cover every configurable subsystem consistently, not just some of them.