3dtours
15fb4422dc
The dust brush filled its hole with a blur of the hole's own rim — the light beside it, carried in. Right for a speck on a wall, and visibly thin over anything with structure: a stroke across a shirt came back as the average of a shirt. The fill is now a learned one. engine/inpaint.ts runs MI-GAN (andraniksargsyan/migan, the same `migan_pipeline_v2.onnx` inpaint-web ships) through onnxruntime-web on the visitor's own machine: 27MB of weights in public/models, WebGPU where the graph fits the provider, the processor otherwise, one warm-up pass so the first repair is not the one that pays for the kernels. It is handed the masked crop and nothing else — the model's mask polarity is 255 KEEP / 0 HOLE, the opposite of the obvious guess, and the other way round repaints the frame and leaves the hole (measured). Step 6e of the renderer cuts the crop at the resolution the model will actually run at (512 on its longest side — the graph is fully convolutional and would take a whole frame, and ten seconds over one), builds the mask from the brush's own circles, and draws the answer into the fill surface at its own place in the box. The composite, the feathered mask and the untouched frame around it are unchanged, so nothing outside the mask moves — and when the model cannot be had the blurred fill is still built first and still stands. The preview gets this for free: renderPhoto was already async and the preview was already debounced. Node probe: the model + polarity + read/write path run; heal-check.mjs keeps measuring the fallback and now asserts the wiring and the polarity. Browser: engine/inpaint.ts in a real Chromium returns a patch (hole moves, kept pixels within 0.02 of a level), and the built app renders a 42-spot stroke in 4.7s on single-threaded wasm with no fallback warning — 1.15s and the warning when the model is taken away.
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.