Deploy / deploy (push) Successful in 4s
Reads /proc, /sys, and common CLI tools (lscpu, lsblk, lspci, lsusb) to print a YAML block matching data/schema.json: device model (DMI on x86, /proc/device-tree/model on ARM SBCs), form factor (best-effort — battery presence, DMI chassis type, device-tree presence), CPU, RAM, root storage type/size, WiFi chip (PCI, then USB, then falls back to driver name rather than guessing wrong), ethernet. Fields it can't detect (archy_version, install_method, status) are left as clearly-marked TODOs rather than guessed. Local-only — no network calls, changes nothing. Tested for real on this box (a QEMU VM): correctly identified it as a VM, correctly fell back to "other" with a TODO for form_factor rather than guessing, output validated as parseable YAML. Passes shellcheck clean. Linked from the homepage, report.html, and CONTRIBUTING.md. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
74 lines
3.1 KiB
HTML
74 lines
3.1 KiB
HTML
<!doctype html>
|
|
<html lang="en">
|
|
<head>
|
|
<meta charset="utf-8">
|
|
<meta name="viewport" content="width=device-width, initial-scale=1">
|
|
<title>ArchyHCL — Archipelago Hardware Compatibility List</title>
|
|
<link rel="stylesheet" href="style.css">
|
|
</head>
|
|
<body>
|
|
<header>
|
|
<h1><a href="index.html">ArchyHCL</a></h1>
|
|
<p>Community-reported hardware compatibility for <a href="https://source.archipelago-foundation.org/lfg2025/archy" target="_blank" rel="noopener">Archipelago</a>. Every row here is a real install someone tested and reported — see it on GitHub/Gitea as a plain data file, no login required to browse.</p>
|
|
<p class="cta">
|
|
Tested Archipelago on your own hardware? <a href="report.html">Report it</a> —
|
|
takes two minutes and helps the next person know what to expect before they buy or repurpose a machine.
|
|
</p>
|
|
<p class="cta-secondary">
|
|
Not sure of your exact CPU/WiFi chip/etc.? Run
|
|
<a href="gather-hardware-info.sh">this script</a> on the machine you
|
|
tested — <code>bash gather-hardware-info.sh</code> — it prints most of
|
|
the fields for you, ready to paste into the form above. Local-only, no
|
|
network calls, <a href="gather-hardware-info.sh" target="_blank" rel="noopener">read it</a> before you run it like you should with any script.
|
|
</p>
|
|
</header>
|
|
|
|
<main>
|
|
<div class="controls">
|
|
<input id="search" type="search" placeholder="Search model, CPU, WiFi chip…" autocomplete="off">
|
|
<select id="status-filter">
|
|
<option value="">All statuses</option>
|
|
<option value="working">Working</option>
|
|
<option value="partial">Partial</option>
|
|
<option value="broken">Broken</option>
|
|
</select>
|
|
<select id="form-factor-filter">
|
|
<option value="">All form factors</option>
|
|
<option value="laptop">Laptop</option>
|
|
<option value="desktop">Desktop</option>
|
|
<option value="mini-pc">Mini PC</option>
|
|
<option value="sbc">SBC</option>
|
|
<option value="server">Server</option>
|
|
<option value="other">Other</option>
|
|
</select>
|
|
<span id="count" class="count"></span>
|
|
</div>
|
|
|
|
<table id="table">
|
|
<thead>
|
|
<tr>
|
|
<th data-sort="device_model">Device</th>
|
|
<th data-sort="form_factor">Type</th>
|
|
<th data-sort="cpu">CPU</th>
|
|
<th data-sort="ram_gb">RAM</th>
|
|
<th data-sort="storage">Storage</th>
|
|
<th data-sort="wifi_chip">WiFi chip</th>
|
|
<th data-sort="status">Status</th>
|
|
<th data-sort="archy_version">Archy ver.</th>
|
|
<th data-sort="tested_date">Tested</th>
|
|
</tr>
|
|
</thead>
|
|
<tbody id="rows"></tbody>
|
|
</table>
|
|
|
|
<p id="empty" class="empty" hidden>No reports match your filters.</p>
|
|
</main>
|
|
|
|
<footer>
|
|
<p>Data lives in <code>data/reports/*.yml</code>, one file per report — browse or fork the raw data <a href="https://source.archipelago-foundation.org/ssmithx/ArchyHCL/src/branch/main/data/reports" target="_blank" rel="noopener">here</a>. See <a href="https://source.archipelago-foundation.org/ssmithx/ArchyHCL/src/branch/main/CONTRIBUTING.md" target="_blank" rel="noopener">CONTRIBUTING.md</a> for the two ways to add a report.</p>
|
|
</footer>
|
|
|
|
<script src="app.js"></script>
|
|
</body>
|
|
</html>
|