A settings page an operator can actually use
Prefix-based grouping dumps most keys into an alphabetical wall. A catalogue with tabs, help text and a search — plus a test that fails the build when a migration adds an uncatalogued key.
Tagged “settings”
4 entries
Minimum withdrawals and fees, driven by settings
Compute the fee once, show the net before they confirm, and keep every threshold in the settings table so repricing is not a code change.
An internal credit economy with an admin-set rate
Earn in integer credits, convert to coin only at withdrawal, and keep the rate in settings. Repricing the whole site becomes one field.
A settings table with typed access and one query per request
Everything an operator might want to change belongs in the database, not in code. This is the small layer that makes that painless.