Releases · paragonie/chronicle

Implemented #53 -- You will now be warned if a public key doesn't match what you input (or, if you omit a public key for setting up replication, it will ask you to confirm it before proceeding)
There is now a /replica/{unique_id} endpoint, just to index each replica's contents. (Before: it was a 404.)
Implemented #34 -- You can now configure your Chronicle to paginate the /export and /since endpoints.
Implemented #61 -- You can now configure your Chronicle to cache HTTP responses for a short period of time, to help mitigate extreme load (i.e. what we've been experiencing in our public instances).

The first record in a Chronicle now has a prevhash of NULL. This allows foreign key constraints to be added to the database table definition.
When publishing files to the Chronicle, anything that cannot be safely encoded in JSON will cause the write to fail.
- This is preferable to causing the export API to break forever.
- We recommend base64url-encoding any binary blobs before sending them to Chronicle.
We now have documentation for Chronicle's internals.
New feature: concurrent instances
Several command line scripts return JSON messages if you pass the -j flag, to make them more useful in automation scripting (without forcing users to parse the standard CLI output messages manually).

Provide feedback