28fd97bcf3
Same issue as the cards just removed from cream-elegance: a hardcoded ['РЫБНЫЕ','МЯСНЫЕ','ВЕГЕТАРИАНСКИЕ','САЛАТЫ','ДЕСЕРТЫ'] tab row that had nothing to do with what was actually in the order (an order with zero vegetarian items still showed a "ВЕГЕТАРИАНСКИЕ" tab as if active/relevant). Now derives the chip row from the distinct categoryName values actually present on the order's items, and renders nothing if that data isn't available. Verified this pass end-to-end rather than just by inspection: - Real "Скачать PDF" pipeline (sunClientOfferDebugPdf) produces a valid application/pdf blob with a correct %PDF-1.4 header, not just canvases. - Confirmed Canvas text genuinely falls back through the font stack (measured identical metrics for an unregistered font vs. Georgia directly, and document.fonts.load() resolves instantly for a never-registered family) -- so a blocked/unreachable Google Fonts degrades silently to Georgia/Arial instead of hanging or erroring, which matters given this app already had to work around Russia connectivity issues elsewhere. - Re-rendered all 6 templates against deliberately adversarial data (150+ word event name, 44-char client name, 350 guests, a million-ruble price, an item with no photo/price/category, a long promo code) -- no crashes, no overlap, graceful ellipsis truncation throughout. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> |
||
|---|---|---|
| .github/workflows | ||
| docs | ||
| ops | ||
| public | ||
| supabase/functions | ||
| tests | ||
| .gitignore | ||
| deploy-trigger.txt | ||
| GITHUB-CLOUDFLARE-SETUP.txt | ||
| package-lock.json | ||
| package.json | ||
| PUSH-TO-GITHUB.bat | ||
| README.md | ||
| TIMEWEB-APP-PLATFORM.md | ||
| UPDATE-FROM-REMOTE-AND-PUSH.bat | ||
| wrangler.jsonc | ||
Caterium
Caterium catering SaaS frontend with Supabase backend.
Production
Primary production URL: https://app.caterium.ru
Production frontend is hosted on Timeweb Cloud App Platform:
- repository:
pavlov346346-source/caterium-app - branch:
production - publish directory:
public - auto deploy: enabled for
production
main is the integration branch. GitHub Actions runs the full Caterium QA workflow for each push to main. Only a successful QA run may promote the verified commit to production.
The Cloudflare Worker ancient-sound-04ab is retained only as a fallback. It is not the primary production target and must not replace the Timeweb deployment unless an intentional fallback procedure is being used.
Deploy checks
npm ci
npm audit --audit-level=high
npm run check:deploy
npm run test:e2e
The QA workflow performs these checks automatically. High/critical npm audit findings block promotion.
Cloudflare fallback
Use Cloudflare only as a backup deployment target. Manual fallback deployment is available as:
npm run deploy:cloudflare-backup
When configuring Git-based Cloudflare fallback deployment, use the verified production branch rather than main so the fallback receives the same QA-approved commit as Timeweb.
Backend
Supabase Edge Functions are versioned under supabase/functions/.
SQL migration/history files live under ops/sql/.
Database DDL changes should be applied as migrations and kept in repository history.
See TIMEWEB-APP-PLATFORM.md for the production hosting checklist.