Documentation Index
Fetch the complete documentation index at: https://mintlify.com/himansaBro/JungleConfig/llms.txt
Use this file to discover all available pages before exploring further.
JungleConfig’s storage backend is chosen at construction time through four factory methods and constructors on the JungleConfig class. All four modes expose exactly the same public API — the only difference is where and how entries are persisted. Picking the right mode lets you balance security, durability, and convenience without changing any application code.
File
Encrypted
InMemory
FlatJson
JungleConfig config = new JungleConfig(new File("app.conf"));
key:TypeName=URLencodedValue line. The file is created automatically on the first write. Because the format is plain text, you can inspect and edit it with any text editor, track it in version control, or diff it between deployments.JungleConfig config = JungleConfig.EncryptedConfig(new File("app.conf"), "password");
JungleConfig config = JungleConfig.InMemoryConfig();
NativeInMemoryIOHandler as its backing store, so no data ever touches the file system. All entries are lost when the process exits. This mode is ideal for unit tests, integration tests, and short-lived CLI tools where you want the full JungleConfig API without any I/O side effects.JungleConfig config = JungleConfig.FlatJsonConfig();
NativeFlatJsonConverter with a NativeInMemoryIOHandler as its backing store. Instead of the line-oriented JConfig001 encoding, the entire internal TypeMap is serialized as a Jackson JSON document and stored in memory. Because the backing store is in-memory, no data is written to disk and all entries are lost when the process exits. This mode is useful when you need an in-process config store or want to inspect the internal state as a JSON structure during debugging.Mode Comparison
| Mode | Persistent | Encrypted | Human-readable | Best use case |
|---|
| File | ✅ Yes | ❌ No | ✅ Yes | Production app config |
| Encrypted | ✅ Yes | ✅ Yes (AES-256/GCM) | ❌ No | Secrets & credentials |
| InMemory | ❌ No | ❌ No | N/A | Tests & ephemeral config |
| FlatJson | ❌ No | ❌ No | ❌ No | Debugging & structured in-process config |
All four modes share an identical JungleConfig API. Methods like Set, get, Get, BeginTransaction, Commit, Rollback, InvalidateCache, and Backup behave the same regardless of which mode is active. You can swap modes by changing a single line of construction code without touching any other part of your application.
