Fix/staging healthchecks - #74
Merged
Merged
Conversation
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.
Description
This PR prepares the infrastructure for a robust production deployment by introducing deep healthchecks and deterministic startup ordering for Docker Compose.
Key Changes
/healthEndpoint: Replaced static response with a full liveness/readiness probe. The API now runsSELECT 1on Postgres andPINGon Redis, returning HTTP 503 if either fails.healthcheckblocks for Postgres, MinIO, Redis, NATS, and the API indocker-compose.staging.yml.depends_on): Replaced simple dependencies withcondition: service_healthyto prevent race conditions (workers wait until NATS and DB are fully ready).encryption_keyin.env.exampleand.env.staging.examplewith a valid 32-byte base64 string to fix CI test crashes caused by the invalid placeholder.pgadminfrom staging and setmigratetorestart: "no".Validation
/healthendpoint with service isolation