Repository navigation
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
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.
The project now centers on placing disposable SQLite read replicas near regional demand, with Litestream VFS supplying reader data and a persistent writer managed separately. The README, dashboard copy, package description, environment/configuration guidance, and roadmap use that model consistently.
Adds an architecture guide and a validated controller configuration for a dedicated reader app. The guide explains app-wide HTTP metrics, disposable caches, write routing, and temporary protection of every existing serving region during a controlled trial. A capability table distinguishes the shipped placement controller from the planned runnable Litestream example, real-metrics observe-only mode, and replica freshness/warmup gates.
Validation: all 12 existing dashboard tests, full type-check, route lint, and formatting checks pass. The example configuration validates in synthetic and live modes; shipped configuration, local documentation links, and package metadata validate. No live database or Fly infrastructure was changed.