Repository navigation
Conversation
|
|
|
@Philipinho I have added the requested redis check and logging. I would note, that currently the entire application crashes when Postgres and/or Redis connections are lost, so this health check does perform its job - we should probably make the app fail in a more graceful way. I think that should be a follow up to this however. |
It only crashes when the database connection fails during startup after 10 retries. A lost Redis connection will not crash it, both during startup and while running. Redis retries indefinitely. |
|
I could not add my commits here. I created a new branch #64. |
…t#56 Keep the backlog focused on deferred TESTS; the related non-test gaps (model-allow-list, restriction-cache invalidation, server embed-recursion guard, collectPageEmbeds cycle guard, jest DI/lib0-ESM debt) are now tracked as issues docmost#52-docmost#56 and only linked from the backlog. Co-Authored-By: Claude Opus 4.8 <[email protected]>
…docmost#52-docmost#56' (docmost#57) from docs/extract-findings-to-issues into develop
chatModel was a free string accepted with empty/garbage values, failing only at runtime as a provider 503; tighten it (trim + non-empty + max 200). Driver was already @isin(AI_DRIVERS). Collapse the client driver list to one AI_DRIVER_VALUES source and add a contract test that reads the server AI_DRIVERS and fails on client/server drift. Co-Authored-By: Claude Opus 4.8 <[email protected]>
3 participants
Adds a simple health check endpoint that verifies the connection to the database.
This also contains a development server script I personally find helpful, but am happy to remove if you'd prefer.
Closes #49