nxtgauge-gitops/apps/nxtgauge-coming-soon/base/ingress.yaml
sync-test e752326411
All checks were successful
sync-to-github / sync (push) Successful in 6s
feat: wire the coming-soon waitlist form to POST /api/waitlist
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>
2026-08-14 03:58:31 +05:30

54 lines
1.5 KiB
YAML

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: nxtgauge-coming-soon
namespace: nxtgauge
annotations:
cert-manager.io/cluster-issuer: letsencrypt-prod
traefik.ingress.kubernetes.io/router.entrypoints: web,websecure
spec:
ingressClassName: traefik
tls:
- hosts:
- nxtgauge.com
- www.nxtgauge.com
secretName: nxtgauge-com-tls
rules:
- host: nxtgauge.com
http:
paths:
# More specific paths must come first — Traefik matches the
# longest prefix. /api routes to the Rust gateway directly (the
# coming-soon page is a static nginx site with no backend of its
# own — see the "Notify Me" waitlist form's fetch('/api/waitlist')).
- path: /api
pathType: Prefix
backend:
service:
name: nxtgauge-rust-gateway
port:
number: 9100
- path: /
pathType: Prefix
backend:
service:
name: nxtgauge-coming-soon
port:
number: 80
- host: www.nxtgauge.com
http:
paths:
- path: /api
pathType: Prefix
backend:
service:
name: nxtgauge-rust-gateway
port:
number: 9100
- path: /
pathType: Prefix
backend:
service:
name: nxtgauge-coming-soon
port:
number: 80