Skip to main content

estory — read from and write to event stores

$ estory init <IDENTIFIER>
$ estory read <IDENTIFIER>
$ estory write <IDENTIFIER>
$ estory guess <IDENTIFIER>

IDENTIFIER is either:

  • a proper DSN (driver://user:password@host:port/database) ;
  • a file that will be interpreted as a DSN (sqlite:///<FILE>) ;
  • a name matching an environment variable (ESTORY_DSN_<NAME>).

To initialise an event store:

$ export ESTORY_DSN_TMP="sqlite:////tmp/event_store.sqlite"
$ estory init TMP

To write an event to a store:

$ jo stream="uuid" version=1 name="EventName" data=$(jo id=1) unixtime=$(date +%s) | estory write TMP

To read events from a store:

$ estory read TMP
{"stream": "uuid", "name": "EventName", "data": {"id": 1}, "unixtime": 1647876362, "who": "", "id": 1}

To copy events from one store to another:

$ export ESTORY_DSN_TMP2="sqlite:////tmp/another_event_store.sqlite"
$ estory init TMP2
$ estory read TMP | estory write TMP2

To copy only some events from one store to another:

$ estory read TMP | jq '.|select(.id==2)' | estory write TMP2

To modify events while copying them from one store to another:

$ estory read TMP | jq '.|.name="EventNewName"' | estory write TMP2

Metadata

Release files for estory 0.2.2

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Built distribution (wheel)

Table of built distributions (wheels) for estory 0.2.2
File Interpreter ABI Platform Actions
estory-0.2.2-py3-none-any.whl Python 3 none any Details for estory-0.2.2-py3-none-any.whl

Release files / estory-0.2.2-py3-none-any.whl

Download URL estory-0.2.2-py3-none-any.whl
Size 15.7 kB
Tags Python 3
SHA-256 checksum
How to use checksums
ef3a5342ccfdd00d34fe2a3e512e82779452bd9083eab5f4759497ee215793dc
BLAKE2b-256 checksum
How to use checksums
cc49743052105ecb80678ed1636aebdd5f25beb5550d58b5bde52f0eddb8e9e3
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via poetry/1.1.12 CPython/3.9.9 Linux/6.0.10-gnu

Security for estory 0.2.2

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page