wishlist 512M (R-612) and uptime-kuma skips its DB wizard (R-613)

Both measured and red-proofed on 9202 through the product. No image moved.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS

CHANGELOG.md

@@ -1,3 +1,16 @@
+## wishlist fits its first boot; uptime-kuma no longer parks on its database wizard (2026-09-23 night, R-612, R-613)
+
+**No `image:` line moved.** Two template fixes, each red-proofed on scratch guest 9202 through the product.
+
+- **wishlist (R-612):** memory 128M → **512M** (`mem_limit` 512M). Measured on the bench: the first-boot
+  `prisma db seed` peaks at 312–345M and was OOM-killed at 128M on every run (kernel `oom_kill` 3); on
+  9202 at 128M the kill came after the Role/Group rows this time, so the sign-up lie did NOT reproduce —
+  the kill is timing-dependent, and at 512M the seed completes (`The seed command has been executed`).
+  Running, the app uses ~115M — 90 % of the old limit on its own.
+- **uptime-kuma (R-613):** `UPTIME_KUMA_DB_TYPE=sqlite`. Before: the box read `running` while the app's own
+  `/api/entry-page` said `setup-database`. After: `entryPage`, `/metrics` 401 (the real server), the database
+  in `/app/data` (`kuma.db`, `db-config.json` — inside the backed-up volume). The probe is unchanged.
+
 ## The test record: an image move must carry its proof (2026-09-23 night, `09` §6.4 part 4 + the catalog half of part 6)
 
 **No `image:` line moved in this commit.** 21 templates gain an `update_ladder:` (backfill); scripts only otherwise.

templates/uptime-kuma/docker-compose.yml

@@ -13,6 +13,11 @@ services:
     restart: unless-stopped
     environment:
       - TZ=Europe/Budapest
+      # R-613 (measured 2026-09-23): without this, 2.x parks at its SETUP-DATABASE wizard on first boot
+      # — the main server never starts, and the probe's any-answer check calls it healthy. With it the
+      # database choice is made (SQLite in /app/data) and the real server starts: /api/entry-page
+      # answers entryPage, /metrics 401. An install that already chose keeps its data/db-config.json.
+      - UPTIME_KUMA_DB_TYPE=sqlite
     volumes:
       - uptime_kuma_data:/app/data
     networks:

templates/wishlist/.felhom.yml

@@ -14,8 +14,8 @@ catalog_since: "2026-09-21"
 
 # --- Resource hints (displayed on deploy screen) ---
 resources:
-  mem_request: "30M"
-  mem_limit: "128M"
+  mem_request: "120M"
+  mem_limit: "512M"
   pi_compatible: true
   needs_hdd: false
 

templates/wishlist/docker-compose.yml

@@ -1,7 +1,7 @@
 # Wishlist - Családi kívánságlista megosztás
 # Domain: ${SUBDOMAIN}.${DOMAIN}
 # Database: None (file-based)
-# RAM: ~30M (mem_limit: 128M) | Pi-compatible: Yes
+# RAM: ~115M running, 312M peak during the first-boot seed (mem_limit: 512M) | Pi-compatible: Yes
 #
 # Environment variables:
 #   DOMAIN          - Your domain (e.g., demo-felhom.eu)
@@ -33,7 +33,11 @@ services:
     deploy:
       resources:
         limits:
-          memory: 128M
+          # 512M, MEASURED 2026-09-23 (R-612): the first boot runs `prisma db seed`, which peaked at
+          # 312-345M; at 128M it was OOM-killed on every run (kernel oom_kill 3), sometimes before the
+          # Role/Group rows existed — then EVERY sign-up fails and the page says "already exists".
+          # Running, the app sits at ~115M, which is 90% of the old 128M on its own.
+          memory: 512M
     healthcheck:
       # A wishlist képfájlban nincs wget és nincs curl — csak node. A korábbi
       # wget próba ezért soha nem futott le, a konténer véglegesen unhealthy