Download the PHP package milpa/event-store without Composer

On this page you can find all versions of the php package milpa/event-store. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Informations about the package event-store

Milpa

# Milpa Event Store > A tiny **append-only event log** for the Milpa PHP framework, with **zero package dependencies**. Append events, replay a stream, project state from the fold. Two interchangeable stores — **file** (JSONL) and **in-memory** — behind one `EventStoreInterface`. The persistence primitive under Milpa's event-sourced process engine. [![CI](https://github.com/getmilpa/event-store/actions/workflows/ci.yml/badge.svg)](https://github.com/getmilpa/event-store/actions/workflows/ci.yml) [![Packagist](https://img.shields.io/packagist/v/milpa/event-store.svg)](https://packagist.org/packages/milpa/event-store) [![PHP](https://img.shields.io/badge/php-%E2%89%A5%208.3-777bb4.svg)](https://www.php.net/) [![License](https://img.shields.io/badge/license-Apache--2.0-blue.svg)](LICENSE) [![Docs](https://img.shields.io/badge/docs-API%20reference-blue.svg)](https://getmilpa.github.io/event-store/) `milpa/event-store` is the smallest possible seam onto an append-only log: an `Event` is an immutable fact — `streamId`, `type`, `payload`, `seq`, `recordedAt` — and a store's only two jobs are "append durably" and "read a stream back in order". **No ORM, no serializer, no framework coupling** — construct a store with a path (or nothing at all) and call `append()`. `recordedAt` is a UTC-serialized wall-clock observation made by the process constructing a new event. It says when that process's clock observed the record, not when the domain event objectively happened, and it is no more trustworthy than that process and clock. Legacy records replay with `recordedAt === null`; the store never invents their time from filenames, file metadata, or payloads. ## Install ## Quick example Project current state by folding the replayed events yourself — the store never stores state, only the facts it was told: ## Two stores, one interface | Store | Durability | Use it for | |-------|-----------|------------| | `FileEventStore` | Appends one JSON line per event to a flat file, under an exclusive `flock()` so concurrent appenders never interleave partial lines. `nextSeq()` and `replay()` both re-derive their answer from the file itself — a fresh instance pointed at the same path, in a different process or a different request, agrees with every other instance about both "what happened" and "what comes next". | Real persistence — the process engine's durable log. | | `InMemoryEventStore` | An in-process array. Nothing is written to disk; nothing survives past the instance's lifetime. | Tests, and zero-file consumers that don't need durability. | Both implement the same four-method `EventStoreInterface` (`append()`, `replay()`, `nextSeq()`, `streams()`), verified by one shared contract test suite (`EventStoreContractTestCase`) so behavior — sequencing, stream isolation, replay order — never drifts between the two. ## Requirements - PHP **≥ 8.3** - Nothing else — `milpa/event-store` has no package dependencies, Milpa or otherwise ## Documentation **Full API reference: [getmilpa.github.io/event-store](https://getmilpa.github.io/event-store/)** — generated straight from the source DocBlocks and dressed with the Milpa design system. ## Contributing Contributions are welcome — see [CONTRIBUTING.md](CONTRIBUTING.md). Please report security issues via [SECURITY.md](SECURITY.md), and note that this project follows a [Code of Conduct](CODE_OF_CONDUCT.md). ## License [Apache-2.0](LICENSE) © Rodrigo Vicente - TeamX Agency. --- Milpa is designed, built, and maintained by **[Rodrigo Vicente - TeamX Agency](https://teamx.agency/?utm_source=github&utm_medium=readme&utm_campaign=milpa&utm_content=event-store)**.

All versions of event-store with dependencies

PHP Build Version
Package Version
Requires php Version >=8.3
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package milpa/event-store contains the following files

Loading the files please wait ...