Build and validate / build (push) Successful in 1m38s
Modeled on three researched precedents (see README): OpenWrt's Table of Hardware for the browsable sortable/filterable table UX, postmarketOS's working/community/testing tiers for the status field (collapsed to working/partial/broken here), and RaspiBlitz's scattered GitHub-issues approach as a negative example to avoid — hence structured YAML report files validated against a JSON Schema instead of free-text issue threads. - data/reports/*.yml + data/schema.json: one file per report, schema requires `issues` whenever status is partial/broken - scripts/build.py: validates every report and builds site/data.json, fails loudly on bad data (same idea as archy's own validate-app-manifest.sh) - site/: plain HTML/CSS/JS, no framework or build step, fetches data.json client-side — search, filter by status/form-factor, sortable columns, click a row for issues/notes detail - .github/ISSUE_TEMPLATE/hardware-report.yml: structured submission path for contributors who don't want to touch git directly - .gitea/workflows/ci.yml: runs the build/validate step on push and PRs Not yet deployed anywhere — see README's Deployment section. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
23 lines
690 B
YAML
23 lines
690 B
YAML
device_model: "Raspberry Pi 5 (8GB)"
|
|
form_factor: sbc
|
|
cpu: "Broadcom BCM2712 (4x Cortex-A76)"
|
|
ram_gb: 8
|
|
storage:
|
|
type: nvme
|
|
size_gb: 512
|
|
wifi_chip: "Broadcom BCM43455 (onboard)"
|
|
ethernet: "Broadcom onboard Gigabit"
|
|
archy_version: "1.8.4-alpha"
|
|
install_method: netboot
|
|
status: partial
|
|
tested_date: "2026-08-10"
|
|
submitted_by: "example-contributor"
|
|
issues: |
|
|
Example report — replace with a real one. Onboard WiFi drops the
|
|
connection under sustained heavy P2P traffic (Bitcoin IBD); a workaround
|
|
is to run over Ethernet instead. Everything else (Lightning, apps,
|
|
dashboard) works fine.
|
|
notes: |
|
|
NVMe via the official PCIe HAT. Boots noticeably faster than SD-card
|
|
installs.
|