ESP32-S3 Bench Guide
ESP32‑S3 N16R8 벤치 가이드: 실시간 핀아웃, 강의, 시뮬레이터 및 벤치 로그
아직 감지된 업데이트가 없습니다. GitHub 릴리스가 나오면 여기에 보입니다.
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.