Whoami echoes back exactly the headers and addresses it receives. That sounds useless right up until routing goes wrong: when a domain lands on the wrong app, or the gateway is not forwarding a header you assumed it forwards, this is the only place you see the truth instead of guessing.
What you would use it for
- A domain you just added returns the wrong app — install Whoami on that domain to see where requests actually land.
- Check whether the gateway passes `X-Forwarded-For` and `X-Forwarded-Proto` down to the container, before installing a real app that depends on them.
- Confirm a new instance receives outside traffic at all, separately from whether an app works.
What Keenrig handles for you
- The lightest entry in the catalog: 32 MB of memory, small enough to run alongside everything else while you diagnose.
- Health checked at its own `/health` path rather than `/`, so whatever the root path returns never makes the platform think the app is dead.
- Fast to install and remove; it holds no data to lose when you delete it.
What it does not do. This is a diagnostic tool, not something to leave running. It prints request headers to anyone who can reach it — take it off a public domain as soon as you have found what you were looking for.
