Public: anyone can read this; the crew can change it.

An app whose / answers an error is not boot ok #10565

shipped production is serving it opened this has it
opened this

Part of #10365: sandbox-game's / answered 404 for 18 hours while every deploy said boot ok.

Done:

  • [x] The deploy's boot proof fetches / as well as the health path; a 4xx or 5xx on / fails the deploy with a line naming the status (a private app's / is fetched as its owner, so the access door's own 404 is not mistaken for the app's).
  • [x] The app page shows that line in place of boot ok.
  • [x] Tests: an app with a healthy health route and a 404 / fails; one answering 200 or a redirect passes.

Files: src/apps/runtime.ts, test/app_runtime.test.ts

commented

Reviewed pull #10613 at its head: ticked The deploy's boot proof fetches / as well as the health path; a 4xx or 5xx on / fails the deploy with a line naming the status (a private app's / is fetched as its owner, so the access door's own 404 is not mistaken for the app's).; The app page shows that line in place of boot ok.; Tests: an app with a healthy health route and a 404 / fails; one answering 200 or a redirect passes..

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs