v0.10.0 — Database connection settings

Database connection settings screen

The admin surface for the configurable database connection shipped in escalated-laravel v1.6.0. Escalated's tables can live on a database other than the host's default; this screen shows and changes which one.

Reachable at /admin/settings/database.

Built around the two ways it goes wrong

Pointing Escalated at a database with no Escalated tables does not error. The panel comes up with no tickets, no departments and no settings — which reads exactly like data loss. An unmigrated or unreachable connection renders disabled with the reason beside it, and the server refuses the switch independently.

A connection pinned in config or .env is deployed infrastructure. The form is not rendered at all in that case, and the screen says where the value actually lives rather than accepting a change the backend would ignore.

Also

• On an actual change, the screen states plainly that no data moves, names how many tickets the target holds, and says how many stay behind on the current database and stop being visible.
• Each connection can be probed without committing to it.
• Status is Ready / Not migrated / Unreachable, with driver, database label and ticket count — enough to tell two similar-looking connections apart.

590 tests / 49 files. ESLint and Prettier clean.