PHPAML

Documentation · Chapter 19

Read the signals from View, Data, and production.

View compilation, database drivers, production permissions, and remote configuration each expose distinct diagnostics. A generic 500 page is not the final evidence.

Every lesson starts from the problem, explains the mechanism, then gives a concrete verification.

LESSON OBJECTIVE

What you will be able to do

Use View overlays, request IDs, Data diagnostics, and production comparisons to locate subsystem failures.

Read the development overlay and logs

In development, the error overlay should name category, message, source line, excerpt, and request ID. Empty closures or unsupported View syntax must fail specifically.

phpaml — zsh
aml data:doctor --connection main --json
aml doctor --production --json

Use Data doctor

data:doctor checks PDO driver, connection, server version, transactions, savepoints, returning, and foreign keys while redacting secrets.

Compare local and production

A local success does not prove deployed PHP version, extensions, case sensitivity, document root, environment variables, writable paths, or database connectivity.

CHECKPOINT

Before you continue

Does the development detail stay out of production responses while remaining recoverable through protected logs and request IDs?