soe
Connects the sqliteonline.com frontend straight to this site's databases: a full SQL console in the browser, nothing to install. This example has it enabled — on sqliteonline.com choose Remote DB and enter url https://your-site/soe/, db name main (the content) or log (the request log) and a CMS account that has the soe flag; the frontend detects the sign-in method itself.
| key | default | description |
|---|---|---|
| path | /soe | URL prefix of the module; must not overlap /cms, static or your routes |
| row_limit | 100000 | max rows per query across all result sets; a number or a string like "100k" / "2m" |
| session_ttl_minutes | 60 | idle lifetime of a console session |
Access is per user and off by default: auth is required, and an administrator ticks the soe checkbox on the admin Users page. Role user gets read-only queries, admin writes too (the engine resyncs its cached counters after a write). Sign-in is the same OPAQUE protocol as the admin UI — the password never leaves the browser; a failed sign-in never reveals whether the login, the flag or the database name was wrong, and attempts are rate-limited.
Only pages on sqliteonline.com may call these endpoints (CORS); the SQL travels directly from your browser to this server. With access_log.mode = "db" the log database is reachable here too — traffic analytics without leaving the console.
Remove the block to disable the module entirely: the routes are not even registered.