mirror of
https://github.com/digital-asset/daml.git
synced 2024-09-20 17:28:46 +03:00
0da814d250
* Stable packages bypass version restrictions. Part of #10029 changelog_begin changelog_end * Add missing bypass * scalafmt * Fix tests * fix script runner * Fix scenario service * Dont make stable packages configurable * unused import * revert unnecessary formatting changes * Added a StableOnly engine mode and a conformance test that uses it * buildifier-fix * Inline LanguageVersions.StableOnly * scalafmt * Remove EngineMode in favor of representing the version range directly * Add -unsafe to flag name * Apply suggestions from code review |
||
|---|---|---|
| .. | ||
| src | ||
| BUILD.bazel | ||
| README.md | ||
Overview
This document is to help internal engineers work with ledger-on-memory.
ledger-on-memory is a key/value-based ledger that uses a simple in-memory map as an
underlying storage. It uses either H2 or PostgreSQL as its index database.
Ledger On Memory
To build a fat JAR with the server built from HEAD run
bazel build //ledger/ledger-on-memory:app_deploy.jar
The application can be run from command line with the following command:
java -Xmx4G -XX:+UseG1GC -jar bazel-bin/ledger/ledger-on-memory/app_deploy.jar --participant participant-id=foo,port=6861
As run from the main project root directory (adjust the location of the JAR according to your working directory).
Alternatively, the application can be run using the Bazel command:
bazel run //ledger/ledger-on-memory:app -- --participant participant-id=foo,port=6861
Creating ledger exports
Ledger On Memory can be used to generate ledger exports through an environment variable:
export KVUTILS_LEDGER_EXPORT=/path/to/export/file
Then launch the ledger using the Bazel or Java command as described above.