Install

ePHPm ships as a single binary that manages itself. There’s no install script — the binary registers and controls its own system service. For trying it out without touching the host, a Docker image is also published.

Docker

docker run -p 8080:8080 ephpm/ephpm:latest

That starts ePHPm with default settings on http://localhost:8080. Mount your document root at /var/www/html and your config at /etc/ephpm/ephpm.toml to serve a real site:

docker run -p 8080:8080 \
  -v /path/to/site:/var/www/html \
  -v /path/to/ephpm.toml:/etc/ephpm/ephpm.toml \
  ephpm/ephpm:latest

Tags

Real SemVer build metadata uses + (v0.0.1+php8.5.2), but OCI tags reject +, so Docker tags substitute - while the upstream + form is preserved on each image’s org.opencontainers.image.version label — the same trade-off k3s and rke2 make.

For the standalone binary install path (single-binary, self-installing, no container runtime needed), grab an archive from Releases and continue with the Linux / macOS or Windows section below.

Linux / macOS

Download the latest binary from Releases and unpack it, then run:

sudo ./ephpm install

install copies the binary to /usr/local/bin/ephpm, writes a default config to /etc/ephpm/ephpm.toml, registers a systemd service (Linux) or launchd plist (macOS), and starts it. By default the server listens on http://localhost:8080.

Variants:

# Install without starting the service
sudo ./ephpm install --no-start

# Skip writing the default config (keep an existing one)
sudo ./ephpm install --no-config

# Install the binary only — no service, no config
sudo ./ephpm install --binary-only

Windows

Download ephpm.exe from Releases. In an Administrator PowerShell:

.\ephpm.exe install

Installs to C:\Program Files\ephpm\, adds the directory to the system PATH, registers a Windows service, and starts it.

Clustered SQLite (sqld) isn’t available on Windows — Turso doesn’t publish a Windows binary. Single-node SQLite, the MySQL/Postgres proxy, and everything else work normally.

Manage the service

After install, the same commands work on every platform — they wrap systemd / launchd / the Windows service controller:

sudo ephpm start          # start the service
sudo ephpm stop           # stop the service
sudo ephpm restart        # restart (after editing the config)
sudo ephpm status         # PID, uptime, last exit code, listen address
sudo ephpm logs           # tail the service log
sudo ephpm logs --follow  # follow new log lines

To run the server in the foreground without registering a service (useful for debugging):

sudo ephpm serve --config /etc/ephpm/ephpm.toml

Uninstall

sudo ephpm uninstall

Stops the service, removes the binary, the service unit, and /var/lib/ephpm/. Pass --keep-data to preserve the config file and any SQLite databases:

sudo ephpm uninstall --keep-data

Build from source

For contributors or custom builds. Requires Rust 1.85+.

# Stub mode — no PHP, fast iteration on HTTP/routing logic
cargo build
cargo run -- --config ephpm.toml

# Release binary with PHP embedded.
# Prerequisites: php-cli 8.2+, composer, git, build-essential, autoconf, cmake,
# pkg-config, re2c, libssl-dev (libssl-devel/openssl-devel on RHEL/Fedora).
cargo xtask release       # → target/release/ephpm
cargo xtask release 8.4   # use PHP 8.4 instead of 8.5

On Windows, cargo xtask release re-invokes itself inside WSL automatically (the PHP SDK build needs a Unix toolchain). Cross-compiled .exe builds work via cargo-xwin:

cargo install cargo-xwin
cargo xtask release --target windows

The first cargo xtask release is slow (it builds a fully static PHP via static-php-cli — about 15 minutes). It’s cached at php-sdk/static-php-cli/buildroot/; delete that to force a rebuild.

A binary built from source can also self-install:

sudo ./target/release/ephpm install

Verify

ephpm --version
ephpm --help
ephpm status