[Push] Serve push requests without loading WordPress - #460
Open
adamziel wants to merge 1 commit into
Open
Conversation
Contributor
Pull pipeline performance —
|
| Stage | PR | trunk | Δ | Status | Details |
|---|---|---|---|---|---|
playground-sqlite-db-pull |
9.45 s | 9.31 s | ⚪ +137 ms (+1.5%) | ✓ | condition=db-pull in PHP.wasm runtime=php.wasm 8.3 wp_mysql_parser=enabled mode=lexer native_lexer=verified native_token_stream=WP_MySQL_Native_Token_Stream native_token_count=18 native_parser=selected trunk: condition=db-pull in PHP.wasm runtime=php.wasm 8.3 wp_mysql_parser=enabled mode=lexer native_lexer=verified native_token_stream=WP_MySQL_Native_Token_Stream native_token_count=18 native_parser=selected |
playground-sqlite-db-apply |
3.62 s | 3.54 s | ⚪ +81 ms (+2.3%) | ✓ | condition=db-apply to SQLite in PHP.wasm runtime=php.wasm 8.3 wp_mysql_parser=enabled mode=parser native_lexer=verified native_token_stream=WP_MySQL_Native_Token_Stream native_token_count=18 native_parser=verified native_ast=WP_MySQL_Native_Parser_Node sqlite_driver_parser=verified trunk: condition=db-apply to SQLite in PHP.wasm runtime=php.wasm 8.3 wp_mysql_parser=enabled mode=parser native_lexer=verified native_token_stream=WP_MySQL_Native_Token_Stream native_token_count=18 native_parser=verified native_ast=WP_MySQL_Native_Parser_Node sqlite_driver_parser=verified |
| Total | 13.07 s | 12.85 s | ⚪ +218 ms (+1.7%) |
Numbers carry runner noise; treat single-run deltas as directional, not authoritative.
📈 Trunk performance history — commit-by-commit timeline.
adamziel
force-pushed
the
adamziel/standalone-push-route
branch
from
August 6, 2026 10:57
20b1b2a to
b96c66a
Compare
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.
Files-push can now use a standalone PHP route that remains reachable when pushed code prevents WordPress from starting.
Background
Before this PR, every push request used the WordPress front controller. A push could install a plugin which throws during WordPress startup, and the next push could not reach
push_createto replace it.This change
The exporter plugin now exposes
push.php, which authenticates and dispatches every push operation without loading WordPress. While WordPress is healthy, it writes the current connection token, push authorization, document root, reprint directory, exclusions, and request limits to a mode-0600 private configuration file. Revoking push blocks new work while retaining the existing durable-commit recovery rule.files-pushaccepts that route through--push-url. The positional remote Reprint API URL still selects the remote state directory and shared local index used by pull, diff, and push. An active sender records its push URL and refuses to resume through another route.The existing WordPress push route remains available for compatibility. Hosts which block direct plugin PHP execution must allow
push.phpor provide another route which does not load WordPress.Testing
The endpoint test pushes a plugin which breaks WordPress startup, confirms the WordPress route returns 500, then runs another files-push through
push.phpand confirms the safe plugin replaces it. It also covers connection-token authentication, revoked authorization, excluded paths, and shared local-index ownership.Supersedes #378.