Runtime Profile

channel: production
api: v1
backend: php-mysql
entry: /public/index.php
router: /public/.htaccess (extensionless URLs)

Request Flow

Browser
  -> Apache/Nginx + PHP runtime
  -> /public/.htaccess route mapping
  -> PHP endpoint (/api/* or docs page)
  -> bootstrap config + DB connection
  -> JSON/HTML response

Public APIs

GET /api/health   -> health + DB connectivity
GET /api/version  -> language/site/version metadata
GET /api/apps     -> app registry (MySQL table tn_apps)

All APIs return JSON and disable cache.

Backend Files

web/tn_site/public/api/health.php
web/tn_site/public/api/version.php
web/tn_site/public/api/apps.php
web/tn_site/lib/bootstrap.php
web/tn_site/config/version.json

TezzNative ↔ Backend

TezzNative CLI + SDK: compiler/runtime toolchain
Website backend: docs, install endpoints, operational APIs
TezzDB path: app/service metadata persistence

Current contract: CLI users discover docs/install from this portal, and backend APIs expose runtime status.

Production Checklist

1) Configure /config/db.php with TezzDB credentials
2) Verify /api/health is ok=true
3) Run: tezz doctor && tezz test --smoke
4) Deploy via tools/deploy_tezzcorp.sh
5) Validate /docs, /docs/sdk, /docs/backend, /docs/tezzdb