Repository navigation
Add Stage 53 community website constructional suggestions - #79
Closed
cursor[bot] wants to merge 1 commit into
Closed
cursor[bot] wants to merge 1 commit into
cursor[bot] wants to merge 1 commit into
Conversation
Record four tree-checked contracts: one update entry point, authenticated service probes, a Pi-hole backup that does not refresh gravity, and a start-time secret gate that sees every published default. Co-authored-by: TechUties Research <techuties@users.noreply.github.com>
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 publishable Stage 53 website markdown under
suggestions/website/for four defects checked against the tree on 2026-10-07. The pages extend./tu-vm.sh update, the audio-config credential helper, the Pi-hole volume backup, andgenerate_secrets. They do not add a suggestion queue, a second updater, or a new secret store.scripts/safe-update.shis documented as a wrapper for./tu-vm.sh updatebut still carries its own pin table, which omitsn8n_mcp.verify_data_retention,scripts/daily-checkup.sh, andscripts/switch-pdf-loader.shopen Postgres and Redis without the password the audio probes already pass.create_backuprunspihole -g, which downloads blocklists into the live resolver, and saves that log as a backup.env_has_insecure_valuesandvalidate_securitymiss published defaults thatgenerate_secretsalready knows how to replace, including the public n8n encryption key.Scope
Docs only. New files:
suggestions/website/index.mdsuggestions/website/safe-update-wrapper-contract.mdsuggestions/website/service-probe-credentials-contract.mdsuggestions/website/pihole-backup-gravity-contract.mdsuggestions/website/startup-secret-gate-contract.mdHistorical hubs (
suggestions/README.md,suggestions/index.md,suggestions/implementation-backlog.md) are unchanged so open stage PRs do not conflict.Release notes (maintainers)
Documentation only. No changelog label required unless maintainers want it under documentation.
Security & RFC
.envvalues in repo or CI logs.The pages name published Compose defaults that are already in
docker-compose.yml. This PR does not change Compose, Nginx, or the helper.Verification
set -a; . ./env.example; set +a; ./scripts/pre-push-check.sh(passes; missing runtime TLS and allowlist files are the expected warnings)git diff --checktitle,description,last_updated,owner,status) on the new pagesenv_has_insecure_valuesawk does not flag the published n8n hex key, WebUI secrets, orSwissPiHole2024!when Postgres is already uniqueOFFICIAL_UPDATE_IMAGE_PAIRSincludesn8n_mcp;PINNED_IMAGE_SOURCESdoes not./scripts/smoke-test.sh --livewas not run. Nginx is not up in this environment.