SOQ International Academy

Debugger

Technical operators enable temporary diagnostics for SOQ International Academy. Readable Source does not expose a dedicated Admin Debugger settings page; runtime debug follows environment configuration (for example APP_DEBUG).

debugger screenshot

Live screenshot from the SOQ beauty demo (aiacademy.aiee.dev).

Surfaces, roles and current terminology

SurfaceCurrent navigation terminologyStatus
Environment debug flag.env ? APP_DEBUG (and related app env)Server / env — no Admin form in readable code
Exception handlingApplication exception handler respects env debugCore
Admin troubleshootingConfigured Admin URL + server logsOperational
Docs referenceThis Debugger guideDocs; do not invent a missing Admin menu

Permissions, settings and activation

  • Only infrastructure or lead admins should enable verbose debug on non-production first.
  • Never leave APP_DEBUG enabled on a public production site.
  • Feature stubs (Feature not activated) are not fixed by enabling debug.

Core workflows

Enable diagnostics safely
  1. Reproduce the failure and note the exact URL and timestamp.
  2. On a staging copy, set APP_DEBUG appropriately in the environment and reload the failing request.
  3. Capture the exception message and stack without publishing it to end users.
  4. Turn debug off again before returning the environment to general use.
Investigate without public debug
  1. Keep APP_DEBUG false on production.
  2. Read PHP/web server and Laravel log files from the host.
  3. Correlate with Maintenance status, recent Update, and activation status rows.
  4. Escalate to soq.edu.sg with sanitized log excerpts if the fault is product-side.
Close out after a fix
  1. Confirm APP_DEBUG is false in production.
  2. Clear caches if configuration was changed.
  3. Retest the original Admin or public flow as a normal user role.

Result states

  • Success: Root cause identified, debug disabled on production, and the user-facing flow works.
  • Pending: Issue reproduced only intermittently or waiting on hosting log access.
  • Denied: Operator lacks server/.env access; Admin UI alone cannot toggle this in current Source.
  • Error: Debug left enabled in production or logs reveal secrets; rotate credentials and disable debug immediately.

Operational notes

  • Status: no dedicated Admin ? Configuration ? Debugger screen was found in readable Blade/PHP; treat older screenshots as outdated.