ladill-qr-plus

4 Commits

Include renames

Author	SHA1	Message	Date
isaacclad	5bab0fedaf	Use Host-header loopback for billing force_ip. Deploy Ladill QR Plus / deploy (push) Successful in 1m45s Details CURLOPT_RESOLVE was not reliably faster; rewrite the billing base URL to the forced IP and send the original Host header instead.	2026-07-16 21:28:06 +00:00
isaacclad	02e6778ccf	Speed up QR create/update by cutting billing round-trips. Deploy Ladill QR Plus / deploy (push) Successful in 2m2s Details Create was making three sequential public HTTPS billing calls (~400ms each) while holding a DB transaction open for image generation. Use loopback DNS forcing, cache balances briefly, return balance from debit, regenerate images only when style changes, and keep remote work outside the DB transaction.	2026-07-16 21:25:16 +00:00
isaaccladandClaude Opus 4.8	b7adb69245	Point in-app wallet top-up at the billing API (key the app already holds) Deploy Ladill QR Plus / deploy (push) Successful in 33s Details qr-plus authenticates to the monolith with a billing service key, not an identity key, so the modal's top-up now goes through BillingClient::topup -> POST /api/billing/topup. Drops the unused IdentityClient::walletTopup. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-06-26 06:23:03 +00:00
isaaccladandCursor	cd6571f199	Extract Ladill QR Plus as standalone app at qr.ladill.com. Deploy Ladill QR Plus / deploy (push) Failing after 1s Details Utility QR types only (URL, WiFi, link list, business, app download) with SSO, Billing API integration, public /q resolver, and qr-plus:import for platform migration. vCard and commerce types stay on the platform. Co-authored-by: Cursor <cursoragent@cursor.com>	2026-06-06 21:31:24 +00:00