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.
ARTIFACT

Runtime and artifact

An artifact is the downloadable ZIP with build output. Runtime is the Go/PHP compatibility layer needed by generated code to behave close to PHP.

Artifact contents

  • Compiled binary with the selected name.
  • Build logs and manifest/checksum when enabled.
  • README_RUN with short run commands.
  • Support files required by the generated output.

What runtime means

  • Go helpers for PHP semantics: arrays, strings, files, and web APIs.
  • Runtime is linked during generation/build; it is not a PHP interpreter.
  • If the project uses an unsupported function, compiler/runtime will show it in the log.
  • Runtime version matters for reproducible builds and diagnostics.
Artifact is not the source ZIP

The downloaded result is build output. Do not store secrets in it and do not use it as a backup of the source project.

What the ZIP contains after build

The artifact contains README_RUN.md, manifest.json, SHA256SUMS and deploy/nginx/php2go-binary.conf so users can verify checksums and place the binary behind Nginx.