Documentation
¶
Overview ¶
Command tally-console serves the read-only demo console.
It reads its configuration from the environment, refuses a configuration it cannot honor, and then serves the console's pages on the configured port, bound to the loopback address alone. The process holds an admin token and has no sign-in of its own, so whoever reaches the port reads everything the token reads. The token has to carry the admin role, because the dead-letter list the overview reads is admin-only.
The pages come from two places: the Reporting API over HTTP, and the engine database, which is opened for reads only. Its pool connects lazily, so the process comes up while the database is unavailable and the pages that read it report the outage.
SIGINT and SIGTERM begin a graceful shutdown: the server stops accepting connections, in-flight requests get a bounded budget to finish, and the process exits zero.