Download the PHP package accordsync/server without Composer

accordsync/server

The Accord sync server for PHP, on PostgreSQL.

A framework-agnostic PSR-15 request handler for GET /health, POST /v1/push and GET /v1/pull: push and pull, scopes, JWT auth, limits, rate limits, CORS and compaction. It speaks the same protocol, merges by the same rules and uses the same PostgreSQL schema as @accordsync/server, so the TypeScript, React Native, Flutter and Python clients sync with it unchanged.

In a Laravel or Symfony app, use accordsync/laravel or accordsync/symfony: they wire this package into the framework (routes, config, database connection, cache, console commands). This page is for plain PHP, or for another framework.

Install

PHP 8.3+ with pdo_pgsql, and PostgreSQL (the conformance suite and the example apps use PostgreSQL 16). The handler needs a PSR-7/PSR-17 implementation; the example below uses nyholm/psr7 and nyholm/psr7-server.

Define the server

AccordServer::define() takes the same parts as defineServer in TypeScript: the schema, a scope function per record type, the access a user gets from their JWT claims, and how tokens are checked. It checks at once that every record type has a scope function. Keep the definition in a file that returns it, so the front controller and vendor/bin/accord compact share it:

Optional arguments: cors (browser origins allowed to call the API), rateLimit (a RateLimits; default 600 requests a minute per device and 1 800 per user; false turns it off), compaction (a Compaction: device TTL, interval, minimum ops) and limits (a Limits: body size, ops per push, pull page size, scope delta size, clock skew). Auth::hs256($secret) is for development and tests.

Serve it

AccordServer::handler() returns a Psr\Http\Server\RequestHandlerInterface. It routes on the request path, so mount it where the path it sees is /health, /v1/push or /v1/pull.

ACCORD_DATABASE_URL is a URL like postgres://user:password@host:5432/db. Each PHP worker handles one request at a time, so the worker pool size bounds concurrent pushes.

Migrations and compaction

Run accord compact from cron at the definition's compaction.intervalMs (default hourly). It takes PostgreSQL's exclusive advisory lock, so overlapping runs, or several servers, do not conflict. In code: AccordServer::migrate($pdo) and AccordServer::compact($definition, $pdo).

One database, any Accord server

The migrations are the TypeScript server's, recorded in the same ledger table (kysely_migration): a database migrated by @accordsync/server is up to date here, and the other way round. One database can be served by TypeScript and PHP servers at the same time, with clients sent to either. The repository's interop/ harness does exactly that: TypeScript devices send every request to a randomly chosen server, through a network that loses requests and responses, and must end with identical data. The repository's Laravel and Symfony example apps also pass Accord's black-box HTTP conformance suite, the same one the TypeScript server passes.

Security notes

• Requests authenticate with Authorization: Bearer <jwt>. In production use Auth::jwks() with an issuer and an audience; pass a PSR-16 cache so PHP workers share the downloaded keys.
• The default rate limiter keeps buckets in memory, which under PHP-FPM lasts one request: use FileRateLimiter on one host, and a shared store on several (the Laravel and Symfony packages use the framework's cache).
• Request bodies above limits.maxBodyBytes (default 5 MiB) get 413; PHP's own post_max_size still applies before it.
• CORS for the sync API is the definition's cors list, answered by the handler.
• What a user may read and write is decided only by your access function and scope functions. See docs/security.md.

Docs: accord.benhattab.pro/docs/php · Source: crossben/accordsync-php · Licence: Apache-2.0