External/oott
1
0
Fork 0
mirror of https://github.com/rzuasti/oott.git synced 2026-07-08 19:21:54 +02:00
Code Issues Packages Projects Releases Wiki Activity

Deploy push relay: dev-shell tooling, real relay URL, /health route

Browse Source 
- flake.nix: add nodejs_22, firebase-tools, and google-cloud-sdk to the dev
  shell so the relay can be tested, built, deployed, and administered locally
- backend settings: point default_relay_url at the deployed relay
- rename the relay liveness route /healthz -> /health: Google Front End
  reserves /healthz and returns its own 404 before the request reaches Cloud
  Run, so the probe was unreachable (verified live; /v1/push and the FCM path
  work end-to-end)

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
rzuasti
2026-06-08 14:00:09 -04:00
co-authored by Claude Opus 4.8
parent 4f3fe10332
commit d81eba3b37
8 changed files with 28 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files
push_relay/README.md
+2 -1
View File
@@ -29,7 +29,8 @@ full design and rationale.
"body": "..." } }`. Returns `{ "results": [{ "token": "...", "status":
"ok" | "unregistered" | "invalid" | "error" }] }`. The backend prunes tokens
reported `unregistered` or `invalid`.
- `GET /healthz` — liveness, returns `200 ok`.
- `GET /health` — liveness, returns `200 ok`. (Not `/healthz`: that path is
reserved by Google Front End and never reaches the function.)
Protection (Phase 1, no shared secret): FCM project scoping (the relay can only
reach OOTT app installs), per-source-IP rate limiting, and a billing cap.