Documentation

php2go 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.
SUPPORT

How to contact support

The more precise the ticket, the faster support can separate a project issue from a compiler bug or unsupported PHP behavior.

Repeat diagnostics first

Run report, check, and deps. If compile fails, keep the last log lines and failure_stage.

Attach a safe snapshot

Use the send-job-to-support button when possible: it sends status, command, stage, last_error, and log tail.

Describe expected behavior

Write which page, command, or endpoint should work and how the result differs from the PHP version.

When an admin is needed

If the issue is about plan limits, access, billing, private settings, or infrastructure, the bot should hand the dialog to an admin.

Do not send secrets in chat

Support does not need real passwords, tokens, private keys, user cookies, or server credentials. Replace them with test values.