Externalize the size limit for LMDB map size for Baser to an environment variable. #810
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR exposes the KERI_BASER_MAP_SIZE environment variable to allow setting the maximum file size for the main KERIpy LMDB database. By default it is set to 100MB, but LMDB documentation suggests on 64-bit systems it is safe to set it as high as a terabyte or more as long as you have the disk space to handle.
You can also change this value and relaunch any process using KERIpy and it will take effect.