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.
Admin and Operations
Settings, migrations, cron on shared hosting, backups and read-only demo mode.
7 entries
A migration runner that is safe to run twice
Numbered SQL files, a table of what has run, and a splitter that does not break on semicolons inside strings.
Run a cron job on hosting that has no cron
A key-gated HTTP entry point plus a lock file, so an external pinger can drive your scheduled work without letting anyone else drive it.
A read-only admin mode over real data
Show a live panel to a buyer, an investor or a prospective moderator without letting them change anything, and without inventing fake data.
Stop two cron runs from overlapping
A non-blocking file lock in three lines, and why a database flag is the wrong tool for this particular job.
Keep the config file out of every release you ship
A sample committed, the real one ignored, the release built by exclusion, and a web server rule that refuses to serve either.
Adjust a member's balance without losing the trail
Every manual adjustment writes a ledger row and an audit row, inside one transaction. An admin panel that edits a balance directly is how books stop balancing.