[HYPER-11] fix: increase healthcheck timeout and document security env vars#29
Merged
[HYPER-11] fix: increase healthcheck timeout and document security env vars#29
Conversation
- Increase Railway healthcheckTimeout from 3s to 10s in case this is an issue. - Document TRUST_PROXY_HEADERS, ALLOWED_ORIGINS, and SECRET_KEY_BASE in the README Configuration section. These were introduced in the security fix (0d95edf) but never documented. - Add .vercel to .gitignore.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
🚅 Environment hyperindex-pr-29 in hypercerts has no services deployed. |
aspiers
changed the title
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
1 participant
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.
Summary
healthcheckTimeoutfrom 3s to 10s — startup takes longer now that 15 lexicons are loaded from the database on boot, causing the healthcheck to fail.TRUST_PROXY_HEADERS,ALLOWED_ORIGINS, andSECRET_KEY_BASEin the README Configuration section. These were introduced in the security fix (0d95edf) but never documented, which caused the 400 errors on the Vercel frontend after redeployment..vercelto.gitignore.Context
After migrating data from SQLite to PostgreSQL on Railway, the service started returning 400 "admin privileges required" errors because
TRUST_PROXY_HEADERSwas not set (it was added in the security fix but defaults tofalse). This has now been set on Railway viarailway variables --set.The healthcheck timeout of 3 seconds was insufficient because the new deployment loads 15 lexicons from the database at startup, pushing boot time past the healthcheck window.