dropyour_release

io.dropyour/dropyour · Verify this server

Publish new content AND check it works, in one transaction. If any check fails, the previous version is put back automatically and you get the failing check plus your app's log lines for that attempt. This is the safe way to ship: the URL never serves a broken version while you figure out what went wrong. Each check is a path and the status you expect (default 200) — 'my page answers', 'my JSON route answers 200', 'the missing route really answers 404'. Rollback needs a version history, which exists on GRADUATED apps (tier 4): on a tier 1-3 drop the release is refused BEFORE publishing rather than leaving you with a broken page and nothing to go back to. onFailure='keep' publishes anyway and only reports; use it when you want to inspect the broken state yourself, or on a drop without version history. The checks are REAL requests: they count as invocations and, if a checked route writes, it really writes. Repeated attempts on the same drop are refused after a few tries in a short window — a publish/fail/republish loop burns your credits and the app's budget without converging.