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.
15 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
An HTTP-triggered job from an external scheduler, a key, a lock and a heartbeat — because a cron that dies silently stops payouts and nothing tells you.
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.
A migration runner that recognises hand-applied migrations
Operators run SQL by hand. If the runner only trusts its own table, it will later insist fifteen applied migrations are pending and lock them out.
Block the admin when migrations are pending
Code that queries a column the database does not have fails with an unstyled fatal. A guard that names the missing migration turns that into a two-minute fix.
The delta release hazard
A delta ships only changed files. If a changed file calls something introduced two releases ago that the operator never deployed, the site fatals on every page.
A web installer whose defaults are a working site
Seed the installer from the settings of a site that already runs. A new install should be usable before the operator has made a single decision.
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.
Head code: let the operator paste what ad networks need
Ad networks require script tags in the head. Restricting what can go there makes the product unusable, so restrict who can set it instead — and keep popunder loaders off public pages.
The CSS that silently breaks pasted ad code
Your ad slot stored and echoed the code perfectly. overflow:hidden, max-width and height:auto then clipped, rescaled and collapsed it.
Integration libraries that return results instead of throwing
A low balance, a daily cap and a rate limit are normal faucet flow. Wrapping every call in try/catch to branch on them reads worse than returning a result array.