Nxtgauge GitOps Configuration
e752326411
All checks were successful
sync-to-github / sync (push) Successful in 6s
Backend endpoint already deployed (nxtgauge-backend-rust apps/users/src/handlers/waitlist.rs, routed through the gateway). - ingress.yaml: route /api on nxtgauge.com and www.nxtgauge.com to nxtgauge-rust-gateway:9100, same 'more specific paths first' pattern nxtgauge-frontend-solid's ingress already uses - the coming-soon page is a static nginx site with no backend of its own. - index.html: handleSubmit now actually awaits the fetch instead of unconditionally showing success after a commented-out example call. Disables the submit button while in flight, added a form-error state for a failed request (was previously just documented, not wired). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> |
||
|---|---|---|
| .forgejo/workflows | ||
| .github/workflows | ||
| apps | ||
| clusters/production | ||
| coming-soon | ||
| docs | ||
| ops | ||
| scripts | ||
| .ci-trigger | ||
| .sops.yaml | ||
| .test_push | ||
| OTP_ISSUE_FIX_PROMPT.md | ||
| ROUTE_ISSUE_ANALYSIS.md | ||