COColosseum

Data Handling

How match data, cache data, and Colosseum account data move through the website.

Data Flow

Browser pages request data from this site's PHP API bridge under /api.
The PHP bridge fetches public IOSoccer JSON, normalizes it, and returns only the fields needed by the interface.
Responses are cached locally for short periods. Live match data uses a shorter cache than historical data.
When the upstream source is slow or unavailable, the site may use stale cache or local fallback data where available.

Colosseum Login Data

Discord OAuth is used only to confirm identity for Colosseum features.
The local store keeps Discord profile basics, active session tokens, teams, memberships, invites, and admin-issued team tokens.
Session cookies are HTTP-only and are not readable by frontend JavaScript.
Logout removes the current session record and clears the session cookie.

Operational Notes

The cache exists to keep search, ratings, transfers, and match pages responsive on shared hosting.
The server should keep api/hub-config.php private because it contains OAuth credentials.
The data/hub directory is protected from direct web access and is used for local Colosseum storage.
This project does not modify IOSoccer source data; it only presents and enriches it for browsing.