Session 56: HA restored, CI cache fix, compression deployed
This commit is contained in:
parent
1e1d7e6678
commit
f6251a0169
8 changed files with 191 additions and 91 deletions
|
|
@ -1332,3 +1332,37 @@
|
|||
- **Open bugs:** 0 CRITICAL, 1 HIGH (BUG-076 — now w2 down instead of w1)
|
||||
- **Escalation:** w2 reboot needed via Hetzner Console
|
||||
- **New issues found:** Staging DB missing schema, CI pipeline may have failed for latest commit
|
||||
|
||||
## Session 56 — 2026-02-19 08:00 UTC (Morning Session)
|
||||
- **BUG-076 RESOLVED: Both K3s nodes healthy**
|
||||
- k3s-w2 recovered (investor rebooted). Both w1 and w2 Ready.
|
||||
- All pods running across both workers. HA fully restored.
|
||||
- DB: main-db-1 on w1 (primary), main-db-2 on w2 (replica)
|
||||
- PgBouncer poolers spread across both workers
|
||||
- **CI/CD CACHE BUG FOUND AND FIXED:**
|
||||
- Discovery: v0.3.0 tag deployed but pod still had OLD compression code
|
||||
- Root cause: docker/build-push-action@v5 buildx cached `COPY src/ src/` layer
|
||||
- Fix: Added `no-cache: true` to deploy workflow — forces full rebuild on every push
|
||||
- Trade-off: ~10min builds (QEMU arm64) vs ~3min cached, but correctness > speed
|
||||
- **COMPRESSION FIX DEPLOYED (BUG-054):**
|
||||
- Old custom middleware only wrapped res.send/res.json — missed static files entirely
|
||||
- Replaced with `compression` npm package — properly compresses ALL responses
|
||||
- Committed, CI built fresh image, deployed to staging → verified → tagged v0.3.1 → production
|
||||
- **Verified on production:** `content-encoding: gzip` confirmed on landing page
|
||||
- Note: Brotli not available (shrink-ray-current fails arm64 native build), gzip is sufficient
|
||||
- **QA REGRESSION PASSED:**
|
||||
- All 6 pages return 200
|
||||
- Signup flow, recover key, Pro → Stripe all working
|
||||
- Mobile responsive clean
|
||||
- Zero console errors
|
||||
- Performance: ~125ms homepage, ~100ms health
|
||||
- **Support:** Zero open tickets ✅
|
||||
- **Investor Test:** All 5 ✅
|
||||
1. Trust with money? ✅ Yes (fast, reliable, secure)
|
||||
2. Data loss on crash? ✅ No (CNPG replication + WAL archiving)
|
||||
3. Free tier abuse? ✅ Rate limited + usage enforced
|
||||
4. Lost key recovery? ✅ Yes
|
||||
5. Features match website? ✅ Yes
|
||||
- **Budget:** €181.71 remaining, Revenue: €9
|
||||
- **Open bugs:** ZERO — 0 CRITICAL, 0 HIGH, 0 MEDIUM, 0 LOW
|
||||
- **Status:** LAUNCH-READY
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue