Repository navigation
Bootstrap documentation containers from the hosted database - #391
Merged
Merged
Conversation
9 tasks
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.
Fresh documentation services currently clone and index the full documentation corpus. Seed empty storage from a verified snapshot at jsn.jace.pro instead, then check GitHub's branch revision. A matching revision skips both cloning and indexing; future revisions continue through the existing incremental GitHub refresh. Existing volumes are never reseeded, custom Git sources skip the default seed, and unavailable or invalid downloads fall back to Git.
Publish a consistent compressed SQLite backup from the live documentation index and expose its manifest and immutable artifact through the Rails service. Only the documentation database is exported. Startup also prepares a missing snapshot for existing deployments; the hosted service can still bootstrap directly from GitHub.
Validation: lint and all five focused service tests passed, including seed → Git update, unchanged revision without cloning, corrupt download fallback, and retaining the last working database after Git failure. CI additionally runs the full CLI suites on Linux and Windows and the website/shared-engine tests, including public artifact routes.