p2g php2go Cloud
RU UA EN KZ
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.

rocket_launchUpload project support_agentContact support
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.
CLI

Allowed terminal commands

The terminal is intentionally restricted. It does not run arbitrary shell, composer scripts, or PHP code from the archive. Every command passes whitelist and plan limits.

help Show the available commands.
ls [path] List files inside the active ZIP workspace.
pwd Show the safe working path.
php2go report [entry.php] Generate a project report and analysis coverage.
php2go check [entry.php] Check the project without generating a binary.
php2go deps [--json] [entry.php] Show dependencies; --json returns machine-readable output.
php2go compile [--web] [--bin name] [entry.php] Start compilation. Use --web for a web server; set the binary name with --bin.
download Explain how to download the ready artifact after compile.
clear Clear the browser terminal screen.
Why arbitrary commands are blocked

The service accepts third-party ZIP archives, so shell commands, network installs, and arbitrary execution are blocked to protect users, workers, and the server.