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.