Everything you need before uploading a project.
These pages cover the normal user flow from preparing an archive to running the compiled Go binary on a server.
A short explanation of the compiler, build output, and the problems it solves.
account_tree How compilation worksStages from uploaded archive to ready Go binary.
rule_settings PHP compatibilityWhat usually works well and where diagnostics are expected.
speed How to write PHP for faster GoPractices that help the compiler generate direct, fast Go code.
business_center Where php2go is especially usefulReal scenarios where compiling PHP into Go gives clear value.
fact_check How to read report, check, and depsWhat the main diagnostic commands and compiler metrics mean.
folder_zip How to prepare a ZIPArchive structure, what to include and what to keep out.
route Where public/index.php should beWhat an entrypoint is and how to change it for custom projects.
terminal Allowed terminal commandsCommand whitelist available in the cloud terminal.
dns Production deployHow to run the compiled binary on a server safely.
shield_lock Security and privacyWhat can be sent to the service and what should stay outside the archive.
support_agent How to contact supportWhat to attach so a compilation issue can be reviewed faster.
play_circle How to run the binaryWhat to do after downloading the artifact and how to run a web binary.
bug_report Common compiler errorsHow to read typical errors and what to send to support.
speed Upload and build limitsZIP size, file count, timeout, and runner limits.
inventory_2 Runtime and artifactWhat is included in the build result and why runtime exists.
Check the report and diagnostics first, then run compile. It is easier to understand issues before a long build.
php2go report public/index.php
php2go check public/index.php
php2go deps public/index.php
php2go compile --web --bin app-server public/index.php