[GH-ISSUE #588] Database connections could wait for availability instead of failing directly #315

Open
opened 2026-02-25 23:33:56 +03:00 by kerem · 0 comments
Owner

Originally created by @fmartingr on GitHub (Mar 5, 2023).
Original GitHub issue: https://github.com/go-shiori/shiori/issues/588

Databases could use a Wait() where they try to check for database readyness before conecting, instead of just connecting directly (and failing if not ready).

  • This should be configurable behind a flag (--wait-for-db that defaults to false)
  • While doing so, figure out a way to propagate the database state to other shiori domains, so we can create a proper liveness endpoint that returns a non-ok status code if the database is not ready.

From https://github.com/go-shiori/shiori/discussions/587

Originally created by @fmartingr on GitHub (Mar 5, 2023). Original GitHub issue: https://github.com/go-shiori/shiori/issues/588 Databases could use a `Wait()` where they try to check for database readyness before conecting, instead of just connecting directly (and failing if not ready). - This should be configurable behind a flag (`--wait-for-db` that defaults to `false`) - While doing so, figure out a way to propagate the database state to other shiori domains, so we can create a proper liveness endpoint that returns a non-ok status code if the database is not ready. From https://github.com/go-shiori/shiori/discussions/587
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/shiori#315
No description provided.