ESP32-S3 Bench Guide
ESP32-S3 N16R8 bench guide: live pinout, lessons, simulators and the bench log.
翻譯準備中
尚未偵測到更新。GitHub 發布版本後會顯示在這裡。
個人 GitHub 帳號下公開儲存庫的擁有者可以登入並驗證所有權,自行管理介紹,無需管理員核准。
登入並產生驗證檔案,在 30 分鐘內將其提交至此儲存庫的預設分支。其他分支或分叉儲存庫中的檔案無效。然後在下方檢查檔案,即可無需管理員核准直接管理專案。請保留檔案以維持管理權限。
如需登入,將前往登入頁面。登入後請回到此處,再次點擊所選的驗證按鈕。
在專案資料夾中執行 /nomorevibe verify,即可驗證所有權並自行管理介紹。
一分鐘完成驗證The website for Yomidori (ヨミドリ), a companion for whatever Japanese you're reading
翻譯準備中
正在載入完整 README。
檢視完整 README ↗The website for Yomidori (ヨミドリ) — a companion for whatever Japanese you're reading, for iPhone, iPad and Mac. Landing, screenshots, support and privacy pages.
The app itself is open source (MIT) at github.com/vlumi/yomidori. This site is not: the copy, the name and the artwork are all rights reserved (see the app's TRADEMARKS.md). The repository is public for transparency, not for reuse.
Static site, built with Hugo Extended. No JS, no external assets — plain HTML/CSS, in the app's own palette.
The Hugo version is pinned in .hugoversion. Hugo is a
build-time tool, not a runtime — there's no security reason to chase updates,
and a bump is the thing most likely to break the build. So pin it and update
deliberately: bump .hugoversion, run a local build, and commit only if
it's clean. (The box's nginx / OS / certbot are what stay current, not Hugo.)
hugo server # local preview at http://localhost:1313
hugo # one-off build into ./public
The gallery reads its pictures from assets/img/shots/<name>.png and resizes
them at build time; a name without a file shows a labelled placeholder, so the
page lays out before the pictures exist. The names it expects are the ones in
content/screenshots.md; drop the App Store PNGs in
under those names and rebuild.
content/privacy.md is the app repository's
PRIVACY.md under a front matter; when that changes, copy it over again rather
than editing here.
Served by nginx over HTTPS (Let's Encrypt / certbot) on the host for
yomidori.app. deploy.sh does it in one step: it fetches the
pinned Hugo Extended (cached per-version under ~/.local/share/yomidori-hugo,
no root, never the system Hugo), pulls, and builds straight into the web root.
./deploy.sh # pull, build, publish to /var/www/yomidori.app
WEBROOT=/some/other/path ./deploy.sh # override the publish dir
./deploy.sh --no-pull # build the working tree as-is
The build writes directly into WEBROOT (--cleanDestinationDir removes stale
files), so nginx root points at the web root itself (e.g.
root /var/www/yomidori.app;), not a public/ subdir — no repo or source files
ever live under the served path. nginx.conf.example is
the server block to start from.