docs: list the two runtime files the seed steps create - #6
Open
luthermonson wants to merge 1 commit into
Open
Conversation
seed/wp-install.sh writes .wp-admin-credentials and both seed steps append to .seed.log, but neither appears in the layout table. Both are dot-prefixed and 403 over HTTP; say so, and say why the .seed.log redirect is load-bearing rather than cosmetic.
|
ePHPm Preview — ready
Preview updates automatically on each push to this PR. |
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.
seed/wp-install.shwrites.wp-admin-credentialsand both seed steps append to.seed.log, but neither appears in the layout table. Both are dot-prefixed and answer 403 over HTTP — worth stating, along with the fact that the.seed.logredirect is load-bearing rather than cosmetic: without it a seed step is killed by SIGPIPE on its first byte (switchboard#23).No functional change; README only.
Secondary purpose, stated openly: this also puts a live preview back up. Merging #4 and #5 correctly tore theirs down, so there is currently nothing deployed to check against. This preview is the vehicle for confirming that a preview actually demonstrates the three embedded engines — per-site Turso, the KV object cache, and native WebSockets — which has never been verified end to end.