content: catch the site up to pithead v1.19 and the v2 appliance work - #32
Merged
Merged
Conversation
The copy still described the v1.0 launch state. Since then pithead shipped nineteen minor releases and the old "road ahead" (Tor-by-default egress, operator alerts, trends, dashboard control, fleet, deploy-anywhere) all landed — so those move into the Pithead feature grid, the shipped waves retell the v1.0 → v1.19 arc, and the road ahead now showcases Pithead OS: the appliance image, A/B updates, first-boot wizard, and USB config channel in review on develop-v2 (pithead#1057). Also: - hero quick start matches the current README (config.minimal.json) - privacy copy updated: all runtime egress rides Tor behind a fail-closed firewall (shipped in v1.1); FAQ disk sizing matches current README - stat band: 11 services; drop the retired node-starter-stacks promise - the ★ flag becomes a star link on both project cards, showing each repo's star count baked at deploy time by scripts/refresh-releases.py (new data/stars.json — visitors still make zero third-party requests) Co-Authored-By: Claude Fable 5 <noreply@anthropic.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
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.
The landing page still described the v1.0 launch state; pithead is at v1.19.2 with the v2 appliance in review. This PR makes every claim on the page true again.
Copy
develop-v2(pithead#1057): bootable A/B image, health-gated signed updates, first-boot wizard/installer/factory reset, USB config channel — honestly labeled "In review".cp config.minimal.json config.json).★ button
The decorative "★ the star" flag is now a link to each repo on both project cards, showing the live star count (pithead 35, rigforge 3) baked at deploy time by
scripts/refresh-releases.pyinto newdata/stars.json— same best-effort pattern asreleases.json, so visitors still make zero third-party requests.Ponytail review: one noted yagni (
latest_tag()could inline intomain(), −4 lines) — kept for symmetry with the pre-existing script shape.🤖 Generated with Claude Code