setupphp — Command Reference
Find, install, remove or select default Eenos PHP runtimes.
Find, install, remove or select default Eenos PHP runtimes.
Requirements
Run as root on the Eenos server. Use the exact version/package identifier returned by --search or --list. Availability depends on the configured OS and Eenos repository; do not infer support from an example version.
Usage
The following example uses the operation described below; replace example identities and paths before use:
/usr/local/eenos/scripts/setupphp --listArguments and options
| Argument / option | Usage and meaning |
|---|---|
-s, --search | Flag. Show available PHP versions. |
-l, --list | Flag. Show installed PHP versions. |
-i, --install | Value: PHP. Install an Eenos PHP version. |
-r, --remove | Value: PHP. Remove an Eenos PHP version. |
-d, --default | Value: PHP. Set the default server PHP version. |
-b, --buildphpconf | Flag. Rebuild the PHP web server configuration. |
-dh, --defaulthandler | Value: HANDLER. Choices: suphp, cgi, fcgi, fpm. Set the default PHP handler. |
-ph, --phphandler | Value: PHP HANDLER. Set the handler for a PHP version. |
-h, --help displays this parser's help. Selectors in the same mutually exclusive group cannot be combined. The installed version remains authoritative for available options.
Operational effects
--search queries available packages and --list inspects installed PHP versions. Install/remove/default change the server runtime setup. Removing a version can break applications using it.
Choose one operation. A server default does not establish that every existing per-domain application has been switched. PHP handler values are suphp, cgi, fcgi and fpm. --phphandler takes two separate values, PHP then HANDLER. Handler/config rebuilds can affect web serving.
Verify the result
List the installed runtimes afterward and verify applications using the changed version.
Check operation output and the relevant service/application state. Several legacy wrappers exit successfully after logging a handler failure, so a zero shell exit status alone is not proof of completion.