Skip to content

Admin, parser, and live log (SSE)

This page is technical background for the parser stream, proxy behavior, and cancel flow. For step-by-step operator instructions, start with the Admin Center guide.

Running the parser

  • From the Server admin area, use the Run parser (or equivalent) action for a server. The parser reads the gamelog path configured for that server and updates the database.
  • Very large logs may hit PHP time limits on the web host. The source src/contrib/ folder is deployed as contrib/ when you upload the contents of src/; it contains helper scripts you can use in a host-specific batch/CLI setup (see install.md).

Server-Sent Events (SSE) live log

The admin parser UI can use a long-lived text/event-stream connection to append log lines without constant iframe reloads. Implementation: src/admin/parser-sse.php and the template src/templates/admin/parser.html (EventSource in the browser). Shared logic lives alongside parser-core.php / parser-core-operations.php.

Reverse proxies

If you run behind nginx or Apache with buffering or compression, the SSE stream can stall or buffer until the end of the request. The application sets X-Accel-Buffering: no for nginx-style proxies; you should still disable response buffering on that location (e.g. nginx: proxy_buffering off; and/or pass through X-Accel-Buffering: no).

Cancel

A cancel flow exists (parser-cancel.php) with a temp flag; the parser stops cooperatively when possible.

Operations that are still “full page”

Some steps (e.g. FTP password prompts, certain confirmations) are still designed around the classic parser request flow. If the embedded stream is not usable, use the classic parser view or the CLI as appropriate.

More context