add install options pages - #8
Merged
Merged
Conversation
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Replaces the More install options placeholder with an overview page and four sub pages, one per route.
Overview — a table of all five ways in (installer, Docker, PIE, prebuilt binaries, from source), what each one installs (interpreter or extension), and what it suits. Plus the interpreter-vs-extension distinction, since that is the axis the table sorts on.
PIE — installing the extension into an existing PHP with the PHP Foundation's extension installer.
Prebuilt binaries — the interpreter and the extension from the Releases page, with how to work out which of the 80 assets you need (
php -v, thread safety,php-config --extension-dir) and the four file-naming patterns.From source — Linux and macOS, extension and interpreter. Framed as a last resort.
Building on Windows — its own page, because the toolchain is entirely different.
Tested rather than transcribed
Run in containers on Debian/arm64/PHP 8.4, using the documented commands verbatim including the
releases/latest/download/URLs:mode=debug,start_with_request=yeswith no ini file).extension_dir,zend_extension=line, loads,extension_loaded("php_debugger")true.phpize && ./configure --enable-php-debugger && makeproducesmodules/php_debugger.so, which loads clean.Not tested: Windows. Those instructions are transcribed from this repo's own
release.yml(build-php-windows), which is how the released.exefiles are built, and fromconfig.w32. Solid provenance, but nobody has run them from this page — worth a trial on real hardware before relying on it. The--disable-opcache-jitrequirement and theRelease/Release_TSoutput paths both come from that workflow.macOS and Windows details on the binaries page come from the release assets and documented platform behaviour, not from runs.