Libraries tagged by writeas

Prevents corrupted sri-hashes.json in Magento 2 by adding atomic writes and file locking.

Go to Download

Stream-oriented database access for PHP with lazy reusable connections, pipelines, chunk processing and bulk writes.

Go to Download

Writes out version information to the .info.yml files for Drupal projects.

Go to Download

SyslogTarget writes log to syslog.

Go to Download

Writes an Adobe IDML file out of a given content

Go to Download

Give a covey agent (covey.work) a door into your Laravel application: schema, read-only queries and the application log behind a read token, tinker behind a write token, so writes carry their own guard rails.

Go to Download

Writes CSV into string output or a file. Also provides export to XLSX format.

Go to Download

A PHP library and command line tool that reads, edits and writes subtitles, transcripts and chapter lists in more than 30 formats.

Go to Download

Reads and writes Sqons.

Go to Download

Laravel friendly Bard that writes sitemap poetry in xml.

Go to Download

Framework-agnostic page-cache control for Contenir CMS — admin writes a purge signal, Sites read it and flush.

Go to Download

CMS Developed Using Yii2 Framework

Go to Download

Public API documentation for Zippendo. Authenticate using your API token (Bearer token prefixed with zipp_). **Brands (sub-accounts).** An organization can be split into brands, each keeping its own orders, shipments and configuration separate. There are two ways to scope requests to one brand, and NEITHER changes any request body: 1. **Bind the token.** Create an API token with a `brandId` and every request it makes is confined to that brand — reads filtered, writes stamped. This is the recommended way to give a single brand's team its own credential. 2. **Send the `X-Zippendo-Brand` header.** An organization-wide token can scope an individual request by sending the brand's id or slug in this header. Most SDKs let you set it once on the client so every call inherits it. A brand-bound token that receives an `X-Zippendo-Brand` header naming a different brand is rejected with `403 BRAND_ACCESS_DENIED` — the binding is never widened. Omit both and requests cover the whole organization, which is the behaviour of every existing token. Records that belong to no brand carry `brandId: null`. Configuration (carriers, shipping rules, addresses) with a null brand is organization-wide and remains visible inside every brand; orders and shipments with a null brand are only visible organization-wide. List endpoints additionally take a `?brandScope=own|shared|both` parameter to narrow further within whichever brand context already applies. `own` returns only rows assigned to that brand, and requires a brand context — a brand-bound token, a resolved brand session, or the `X-Zippendo-Brand` header above — otherwise `400`. `shared` returns only the organization-wide rows (equivalent to filtering `brandId=none`). The default, `both`, keeps the existing behaviour: a brand context sees its own rows plus the organization-wide ones. Set `X-Zippendo-Brand-Scope` as a client default to apply the same choice to every request instead of repeating the query parameter on each call — an explicit `brandScope` query parameter always wins over the header, and a blank header value is ignored. Brands themselves are managed under the **Brands** tag. Retiring a brand is done with `POST /orgs/{orgId}/brands/{brandId}/archive` — permanent deletion is a dashboard-only action, since it is refused while any order, shipment, member or token still references the brand. Brands require a plan that includes them; creating one beyond your plan's limit returns `403`.

Go to Download

Monolog handler that writes to ZendHQ monitoring

Go to Download

Lightweight PSR-16 file cache with atomic writes and TTL support.

Go to Download