refactor: simplify maintenance banner to NEXT_PUBLIC env var, remove API endpoint#206
Merged
Merged
Conversation
…ctly Removed /api/maintenance endpoint — it was blocked by nginx routing. OutageBanner now checks NEXT_PUBLIC_MAINTENANCE_MODE at build time. Sam just sets NEXT_PUBLIC_MAINTENANCE_MODE=true in the env, rebuilds, and the banner appears — no nginx config changes needed.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Replaced the /api/maintenance endpoint with a direct NEXT_PUBLIC_MAINTENANCE_MODE env var check in the OutageBanner component. No nginx routing changes needed — just set the env var, rebuild, redeploy.