3dtours
8e330ee28b
cc186c4put the news about the trial into the bar, one line, and asked nothing more of it. On the landing page that line is a sentence, not a label: at 1440 it fits, on a phone it wraps into a paragraph and the bar grows a shelf of text above the hero. So the band is drawn as a track and the sentence is set in motion — one line that is never wider than the window because it is never asked to fit in it. It is the same bandcc186c4wrote, moved to the last shelf of the bar, under the menu line rather than beside the header. Two copies of the string ride the track, the second hidden from screen readers so the news is announced once, and the track slides exactly half its own width: the copy that was waiting arrives where the one before it left, so the loop has no seam and the 72px of air lives in each copy's right padding rather than between the two. `width: max-content` on the track is what makes that half-exact — the track is the two copies and nothing else, so -50% is one copy by construction and not by measurement. 40s, linear, infinite; the animation is dropped under `prefers-reduced-motion: reduce`, where the sentence simply sits at the left edge of the band, clipped the way it already is mid-scroll. The colour is the theme's own ink, not the page's amber: the notice is the product's voice about itself, so it wears the accent the rest of the landing page wears and follows the visitor through all five themes. The bare accent is too bright to read on the light theme's paper, though, and the worst pair is itself in the theme set — the bare accent lands at 4.0:1 on the violet dark page, which a 12px line may not wear. So the ink is `color-mix`ed 78% accent toward the page's text colour: the hue that says "theme colour" survives, and the value walks toward whichever extreme the page already uses, which is the one direction that is always safe. Worst pair across the ten theme/page combinations is 5.66:1. The bar is fixed, so the shelf it gained is a shelf the hero has to pay for: `scroll-padding-top` goes 116 to 148 (62px of nav + 43px of subnav + 32px of notice, plus a little air) and the hero's top padding 184 to 216. Below 1160px the subnav is gone and only the notice is owed: 144, up from 112. The numbers are hardcoded rather than measured — the bar's height is a sum of three fixed shelf heights, and a ResizeObserver watching a 32px band would be machinery that reports what the stylesheet already says. Verified: npx tsc --noEmit clean, npm run build clean. In the running app through a probe: navBottom 139.08, subBottom 105.89, notice.top 105.89 then height 32.19, so the band sits directly under the menu line; trackW 1426.625 is exactly 2 x spanW 713.312, so -50% is one copy and the loop is seamless; the transform was observed mid-flight (matrix -12.48 to -39.53 over 1.5s) with overflow hidden and the animation named; h1Top 267.59 clears navBottom 139.08, the same gap the hero had before. At 390x800: noticeTop 62, height 32.19, subnav hidden, one line, no wrap, h1Top 195.59. The band was viewed in both themes and at both widths. Contrast of the mixed ink against each page, all ten theme/page pairs, measured from the rendered pixels: 6.79 / 9.89 / 5.66 / 10.22 / 12.64 light and 10.98 / 7.69 / 12.72 / 6.76 / 5.67 dark. Co-authored-by: PenguinHarness <noreply@penguin.local>
RecipesCam web — self-contained stack
A Docker-hosted web build of RecipesCam. Everything it needs is in this folder: move it to another machine, run two commands, and the app is up. It does not need the React Native project around it.
cp .env.example .env
docker compose up -d --build
# → http://localhost:8090
What runs where
| Service | Image | Role |
|---|---|---|
frontend |
nginx:1.27-alpine (built by frontend/Dockerfile) |
Static SPA + /api/ reverse proxy |
api |
node:22-slim (built by backend/Dockerfile) |
Accounts + saved recipes, SQLite on ./data |
frontend resolves api through Docker's embedded DNS and proxies /api/* to
it — that is why the API container is named api and why it is not published on
the host. Only ${WEB_PORT:-8090} is exposed.
Photos never leave the browser. The CanvasKit render pipeline (grade, frame, watermarks, JPEG encode) runs in the visitor's tab; the API only stores recipes as JSON.
Layout
docker-compose.yml the stack
.env.example WEB_PORT
data/ SQLite (created on first run, gitignored)
backend/ Fastify + better-sqlite3 API, own Dockerfile
frontend/ Vite + React + CanvasKit SPA, own Dockerfile + nginx.conf
shared/ vendored copies of the app's types + utils (see below)
src/engine/ skiaShim.ts (CanvasKit) + exportEngine.ts (render pipeline)
+ session.ts (localStorage/IndexedDB studio persistence)
Vendored files
frontend/shared/{types/index.ts,utils/*.ts} are byte-identical copies of
src/types/index.ts and ten src/utils/*.ts files from the React Native
project (@shopify/react-native-skia is aliased to src/engine/skiaShim.ts in
vite.config.ts + tsconfig.json, so those files compile unchanged):
cinemaShader colorUtils defaultRecipes exifWrite frameUtils jpegDpi
paramDefs recipeShare skiaImage toneShader.
The landing page needs no CDN: frontend/public/assets/fonts/*.woff2 are the
seven self-hosted faces behind the three font groups the Themes menu offers
(Plus Jakarta Sans / Inter / JetBrains Mono, Fraunces / Be Vietnam Pro /
Courier Prime, Be Vietnam Pro / Space Mono — all SIL OFL, pulled from Google
Fonts, vietnamese + latin + latin-ext subsets), and
frontend/public/assets/samples/s*.jpg are the six placeholder negatives the
film strip, preset tester and QR card show (swap them for real graded stills
whenever we have them). Its one foreign request is the QR image from
api.qrserver.com, which degrades to an empty slot offline.
When the app changes one of them, copy it back in — the renderer is only "parity" for as long as these stay in sync:
cd <repo>/docker/frontend/shared/utils
cp <repo>/src/utils/<name>.ts .
Operations
docker compose logs -f api # API log
docker compose restart api # after backend/src changes (rebuild: --build)
docker compose down # stop; ./data survives
Backup is the ./data folder — that is the whole database.
Checks
curl -s http://localhost:8090/api/health # {"ok":true}
curl -sI http://localhost:8090/ # 200, index.html
Then open the UI, drop a photo in, and confirm the preview shows the picture and
EXPORT downloads a JPEG that opens. The preview going solid black while the
export still reports a plausible size is the one failure mode worth knowing: it
means the CanvasKit GPU surfaces lost their shared GrDirectContext (see
frontend/src/engine/skiaShim.ts), and with no GPU the raster fallback renders
the same pipeline correctly, just slower.