mirror of
https://github.com/kuhyx/testsAndMisc.git
synced 2026-11-19 11:34:21 +01:00
The solver only ran behind ./run.sh, had one media query in the whole
stylesheet, and kept the inventory in a 46vh scroll box that showed maybe a
third of the 43 dice. Setting it up on the PC did nothing for the phone.
Deployment
dice.kuhy.duckdns.org, behind the existing gitea-caddy edge. DuckDNS already
wildcards *.kuhy.duckdns.org (checked against 1.1.1.1 and 8.8.8.8), so no
dashboard step. deploy_build.sh builds to dist.staging and rsyncs into dist/
with --delete-after --delay-updates; plain --delete removes stale assets
before writing the new ones, which 404s a client mid-load. A post-commit hook
starts a MemorySwapMax=0 systemd user unit, so a rebuild can neither slow a
commit nor thrash zram.
Three traps found by driving the live URL in a browser rather than curling it:
a site address of "127.0.0.1:8089" reads as a HOSTNAME, so Caddy enabled
auto-HTTPS and started an HTTP->HTTPS redirect listener that bound *:80 next
to the edge -- SO_REUSEPORT would then split inbound HTTP and intermittently
break ACME for every domain here. The same address also made a Host matcher,
so the edge's forwarded Host matched nothing and served an empty 200 while the
local health check passed. And watching dist/'s own inode could never detect a
detached bind mount: rsync into an existing directory never changes it. Each
now has a guard that asserts positively rather than failing open.
Dice list
All 43 on screen at every width, no inner scrollbar. Column count and size
tier are chosen together from a container query on the panel -- not the
viewport, which mispredicts by 2x at the point the columns split. Two
invariants govern it: the list fits above the fold, and the name column stays
wide enough to tell Painter's die B, G and R apart. The left column holds the
grid alone, so it is sized to fill the height it owns: one --die-row value
drives the type, buttons and bar strip, giving a 52px row and 44px buttons on
a 1296px-tall screen and 20px rows on a phone.
Three safe-design rules are broken inside .die-list deliberately: sub-16px
body text, square icon buttons, sub-8px intra-cell gaps. 43 items with a name,
a chart and a counter in one viewport is arithmetically incompatible with 16px.
Import / export
A file, the clipboard, or a link carrying the inventory in the URL fragment.
One validator behind all four entry points including localStorage; it keeps
what it can and reports what it dropped, so a die added in a later game patch
costs you that entry, not the inventory. A link never silently overwrites what
is saved here -- it offers Keep or Discard, and only a link that actually
carries dice is applied at all, because one encoding a count of zero parsed
cleanly, blanked the screen, disabled Clear and left Keep writing the emptiness
over the visitor's own loadout.
session_autopsy
parse.py (551) and report.py (504) were over the repo's 500-line limit, so
test_file_length has been failing on main since 5ffd035. Extracted TurnTracker
and the two candidate-cell helpers. Report output is byte-identical on real
data apart from its timestamp, checked against HEAD in a worktree.
Verified: 288 TS tests and 911 Python tests, 100% coverage both, lint and
pre-commit clean, 8 viewports measured on the live HTTPS site, solver confirmed
through the real module worker.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
108 lines
4.1 KiB
Bash
Executable File
108 lines
4.1 KiB
Bash
Executable File
#!/bin/bash
|
|
#
|
|
# deploy_build.sh — build the static bundle that dice.kuhy.duckdns.org serves.
|
|
#
|
|
# The single build path, used by both setup_kcd2_dice_solver.sh and the
|
|
# post-commit auto-rebuild, so the live site can never be produced two
|
|
# different ways.
|
|
#
|
|
# Why it does not just run `vite build`:
|
|
#
|
|
# The serving container bind-mounts dist/ at /srv. A bind mount follows the
|
|
# INODE, so anything that replaces the directory (rm -rf dist && mv new dist)
|
|
# silently detaches the mount until the container is restarted — the site then
|
|
# serves the old files forever with no error anywhere. And a plain `vite build`
|
|
# empties dist/ before writing, so the site 404s for the length of the build.
|
|
#
|
|
# Building into dist.staging/ and rsyncing into dist/ avoids both, but only
|
|
# with --delete-after --delay-updates: plain --delete removes stale files
|
|
# BEFORE writing the new ones, so a client that fetched index.html moments
|
|
# earlier can 404 on the very asset it is asking for.
|
|
#
|
|
# Preserving the inode is necessary but not sufficient, so the publish is
|
|
# followed by a check that the container is still mounted on this directory —
|
|
# see assert_mount_live for why that cannot be done by watching the inode here.
|
|
#
|
|
# Usage:
|
|
# deploy_build.sh Build and publish into dist/.
|
|
|
|
set -euo pipefail
|
|
|
|
SCRIPT_DIR="$(dirname "$(readlink -f "$0")")"
|
|
readonly SCRIPT_DIR
|
|
readonly STAGING="${SCRIPT_DIR}/dist.staging"
|
|
readonly LIVE="${SCRIPT_DIR}/dist"
|
|
# Must match setup_kcd2_dice_solver.sh's DICE_CONTAINER.
|
|
readonly CONTAINER="kcd2-dice"
|
|
|
|
die() {
|
|
echo "deploy_build: $1" >&2
|
|
exit 1
|
|
}
|
|
|
|
# nvm-installed toolchains are not on PATH for systemd/git-hook invocations.
|
|
ensure_toolchain() {
|
|
if [[ -s ${NVM_DIR:-$HOME/.nvm}/nvm.sh ]]; then
|
|
# shellcheck disable=SC1091 # sourced at runtime, path varies by machine
|
|
source "${NVM_DIR:-$HOME/.nvm}/nvm.sh"
|
|
fi
|
|
command -v node >/dev/null || die "node not found."
|
|
command -v pnpm >/dev/null || die "pnpm not found."
|
|
command -v rsync >/dev/null || die "rsync not found."
|
|
}
|
|
|
|
# Confirm the serving container is still mounted on THIS directory.
|
|
#
|
|
# Watching dist/'s own inode across the rsync cannot detect a detached mount and
|
|
# never could: rsync into an existing directory never changes it, and if dist/
|
|
# had already been removed (it is gitignored, so `git clean -xdff` removes it)
|
|
# the mkdir above recreates it at a fresh inode before anything is measured.
|
|
# Either way the check passes while the container serves the pre-deletion
|
|
# snapshot forever, with no error anywhere. The only thing that actually
|
|
# answers the question is what the CONTAINER sees.
|
|
assert_mount_live() {
|
|
local running host_inode container_inode
|
|
command -v docker >/dev/null 2>&1 || return 0
|
|
running="$(docker ps --format '{{.Names}}' 2>/dev/null || true)"
|
|
grep -qx "$CONTAINER" <<<"$running" || return 0
|
|
|
|
host_inode="$(stat -c %i "$LIVE")"
|
|
container_inode="$(docker exec "$CONTAINER" stat -c %i /srv 2>/dev/null || true)"
|
|
if [[ -z $container_inode ]]; then
|
|
echo "deploy_build: could not read /srv inode from ${CONTAINER}; skipping mount check." >&2
|
|
return 0
|
|
fi
|
|
if [[ $host_inode != "$container_inode" ]]; then
|
|
echo "deploy_build: dist/ was replaced — ${CONTAINER} is serving a detached copy." >&2
|
|
echo "deploy_build: restarting ${CONTAINER} to re-attach the bind mount…" >&2
|
|
docker restart "$CONTAINER" >/dev/null
|
|
container_inode="$(docker exec "$CONTAINER" stat -c %i /srv 2>/dev/null || true)"
|
|
[[ $host_inode == "$container_inode" ]] ||
|
|
die "${CONTAINER} still not mounted on ${LIVE} after a restart."
|
|
echo "deploy_build: ${CONTAINER} re-attached." >&2
|
|
fi
|
|
}
|
|
|
|
main() {
|
|
ensure_toolchain
|
|
cd "$SCRIPT_DIR"
|
|
|
|
echo "Installing dependencies…"
|
|
pnpm install --frozen-lockfile
|
|
|
|
echo "Building into dist.staging…"
|
|
pnpm exec tsc -b
|
|
pnpm exec vite build --outDir dist.staging --emptyOutDir
|
|
|
|
# Fail before touching the live directory, never after.
|
|
[[ -f "${STAGING}/index.html" ]] || die "build produced no index.html."
|
|
|
|
mkdir -p "$LIVE"
|
|
rsync -a --delete-after --delay-updates "${STAGING}/" "${LIVE}/"
|
|
assert_mount_live
|
|
|
|
echo "Published $(find "$LIVE" -type f | wc -l) files to ${LIVE} (inode $(stat -c %i "$LIVE"))."
|
|
}
|
|
|
|
main "$@"
|