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.
Summary
Adds a new
doltlitestorage strategy that uses Doltlite as the branchable SQLite backing store for both WordPress database tables and BranchFS-managed files.This includes runtime routing/bootstrap support, Doltlite control commands, BranchFS branch checkout integration, SQLite Database Integration patches needed for Doltlite branch checkout, static PHP build integration for Doltlite, storage-driver documentation, and performance fixes for Doltlite-backed BranchFS reads/imports.
Validation
scripts/build-dist.shcompleted and the resulting PHP reporteddoltlite_engine() = prolly.FORKPRESS_RUNTIME_BUNDLE=/dev/null cargo test -p forkpresspassed: 21/21.cargo build -p forkpresspassed.forkpress init --strategy doltlitecompleted in about 9.6s after import transaction optimization.200in about 0.65s.200in about 0.65s./site.git.Known follow-ups
This remains a draft because the Git write path still needs work before review-ready status:
forkpress commitis wired but still needs optimization and correctness work in post-push import/commit processing.Manual testing
Expected: init should complete in seconds rather than minutes, and page loads should be fast once the server is running.