Repository navigation
Prepare the status repository for a public showcase - #1
Merged
Merged
Conversation
Remove the Cloudflare account id from the Wrangler config, ignore local secret files, and document the monitored sites and how to run the Worker. Checks now release unused response bodies, unknown paths no longer trigger a probe, and CI runs the tests and a dry-run bundle. Co-authored-by: Gáborjáni-Szabó Ádám <Programcode@users.noreply.github.com>
|
Warning Review limit reachedEnable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. Next included review available in 59 minutes. View limit details
Note 🎁 Summarized by CodeRabbit Free
Comment |
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
This prepares the Pi-Stack status Worker to be shown on a public GitHub profile. It does not rewrite history, deploy, or change repository settings.
The README screenshot is the live page at status.pi-stack.org. The page markup is unchanged. The updated Worker was also run locally: it checked all eight sites, served
/and/api/status, rejected other paths and methods, loaded the page font under the new content security policy, and stayed within the viewport at 390px wide.Live Pi-Stack status page
Safety
gitleaks 8.30.1 and trufflehog 3.99.3 scanned every commit and branch. Neither reported a verified or unverified secret. A manual pass found no
.envfiles, API tokens, private keys, IP addresses, Tailscale names, internal paths, phone numbers, postal addresses, logs, or databases. There are no agent-note files.account_idis removed fromwrangler.jsonc. It is still in the first two commits (5611107,68fa4de), inwrangler.jsonc. It identifies the Cloudflare account. It is not an API token, and it cannot be rotated. Before the next deploy, select that same account withwrangler loginorCLOUDFLARE_ACCOUNT_ID, so Wrangler does not target a different account.The KV namespace id stays in
wrangler.jsonc. Cloudflare documents namespace ids as public identifiers, and the id does not grant access. Dropping it can make the nextwrangler deployprovision a new namespace and leave the live page on empty history.The two original commits use a personal Gmail address as the author. That address will show on those commits if this repository is made public. History was not rewritten. Use GitHub's noreply address for later commits if that Gmail address should not appear again.
What else changed
npm test,npm run lint, andnpm run build(wrangler deploy --dry-run, which does not upload)account_idcompatibility_datestays2026-10-01. Moving it can change runtime behavior, and this Worker is already deployed.None of this is deployed. Traces and the new response headers apply on the next deploy only. Repository visibility, description, and topics are untouched.
To show artifacts inline, enable in settings.