PHP Packages

ePHPm exposes native SAPI functions — ephpm_kv_* for the embedded KV store, ephpm_db_* for the embedded database, and the \Ephpm\Worker\* primitives for worker mode. You can call them directly. Most applications shouldn’t: the packages below wrap them in the API your framework already speaks, so you keep writing ordinary framework code.

All of them are maintained in the ephpm GitHub organization and are MIT licensed.

Installing

These packages are not on Packagist. Distribution is via each package’s GitHub repository as a Composer vcs repository.

Composer does not resolve a VCS dependency’s own VCS repositories transitively, so every ePHPm package in the tree needs its own repositories entry — including packages you did not name in require.

{
  "repositories": [
    { "type": "vcs", "url": "https://github.com/ephpm/db-laravel" },
    { "type": "vcs", "url": "https://github.com/ephpm/db" }
  ],
  "require": {
    "ephpm/db-laravel": "^0.1"
  }
}

Two things to check on the repository before you write the constraint:

• The repo name is not always the package name. The worker base package ephpm/worker, for example, lives at github.com/ephpm/php-worker. Use the repository URL in repositories and the package name in require.
• Not every package has a tagged release yet. A ^0.1 constraint only resolves against a tag; for an untagged package use dev-main (with an appropriate minimum-stability). Check the repository’s releases page.

Every package requires PHP 8.2+.

Database adapters

These route SQL through the in-process ephpm_db_query() / ephpm_db_execute() bridge — no socket, no wire protocol, no PDO. They need an ePHPm build that provides those functions (v0.6.3 or newer) with [db.sqlite] configured.

The stubs shipped by ephpm/db are for your IDE and static analyzer only. They are deliberately not in autoload.files — at runtime the global functions are provided natively by the engine, and autoloading the stub would redefine them and fatal. Point PhpStorm/Psalm/PHPStan at the stubs/ directory instead.

The wire path — pdo_mysql against 127.0.0.1:3306 — remains fully supported and is still the default. These adapters are an optimization, not a migration you are obliged to make.

Cache, KV, and session packages

These route through the ephpm_kv_* SAPI functions into the embedded, cluster-replicated KV store. See KV from PHP for the underlying API.

Each of these requires the ephpm_kv_* functions, which means running under ePHPm; check the individual repository’s README for its own minimum ePHPm version.

ePHPm also has a native session save handler built into the SAPI (session.save_handler = ephpm), which needs no Composer package at all. ephpm/session-handler is the userland alternative for cases where you want the handler under your own control.

Worker-mode adapters

These drive worker mode — boot the framework once per worker thread, then loop on requests.

The three adapters all depend on ephpm/worker, so its repository needs its own repositories entry alongside theirs.

See also

• Database from PHP — the ephpm_db_* bridge these DB adapters wrap
• KV from PHP — the ephpm_kv_* functions the cache packages wrap
• Worker Mode — the engine primitives the worker adapters wrap