Runtime
Choose how OctoPress continues long runs (Loopback or Shell) and set the PHP, Composer, Node, npm and Bash paths.
Open Settings → Runtime (it is also a step in the Pro setup). It explains: "Choose how OctoPress continues runs, then configure local command paths used by worker and development tools."
A badge at the top says Shell driver active or Loopback driver active.
Runtime driver#
| Driver | How runs continue | Best for |
|---|---|---|
| Loopback | WordPress makes requests to itself and each request continues the run. | Limited hosting. Always available. |
| Shell (recommended) | A background worker process continues the run. | Reliable long runs, Schedules, builds and shell tools. Available only if your host allows starting processes. |
If Shell is unavailable the card shows Unavailable with a reason in red. A warning may also appear if PHP time limits are low.
Binary paths (Shell)#
When Shell is selected, check these paths. Each row shows Available or Unavailable and the detected version.
| Binary | Required |
|---|---|
| PHP | Yes. Must be a command-line PHP. |
| Composer, Node, npm, Bash | Optional. Needed by the matching tools. |
In the setup step, Detect binaries fills in what it finds, and Save and check confirms the driver. Click Save on the Settings tab.
With Loopback, no paths are needed: "Loopback mode does not require local binary paths."
Choosing#
- Use Shell when it is available. Long answers are less likely to stop halfway.
- Stay on Loopback if your host blocks processes, and make sure loopback requests and WordPress cron work. See Common problems.
- Scheduled scripts and the development shell tools need Shell.