p2g php2go Cloud
loginLogin rocket_launchStart
Documentation

php2go Cloud documentation

A practical user guide: prepare a ZIP, choose an entrypoint, run allowed commands, download the artifact, and understand common compiler errors.

Fast path to the first build
  1. Pack the project into a ZIP without secrets or junk files.
  2. Make sure the entrypoint exists, usually public/index.php.
  3. Run report/check/deps before compile.
  4. Download the artifact and run the binary using README_RUN.
ERRORS

Common compiler errors

If a build fails, open the job, check the last log lines, and send a support ticket with the attached log.

Entrypoint not found

The file passed in the command does not exist inside the active ZIP. Check archive structure or the project default entrypoint.

Function/class not found

The compiler could not find a function, class, or namespace. Common causes are incomplete vendor, wrong autoload, or conditional includes.

Unsupported extension

The project uses a PHP extension or runtime function not yet supported by php2go runtime. Send the log to support to find a workaround.

Duplicate class/function

The same symbol is included twice. Check autoload, manual require calls, and vendor files.

Timeout or memory limit

The build exceeded time, memory, or process limits. Reduce the archive, inspect dependencies, or upgrade the plan.

Payment/limit blocked

The command was blocked by plan limits, an expired subscription, or exhausted one-time compile quota.

Do not copy logs manually

The job page has a send-log-to-support button. It attaches a safe snapshot: command, status, last_error, and recent log lines.

support_agentContact support