Releases: maxpert/marmot
v0.8.3-beta.1
Full Changelog: v0.8.2...v0.8.3-beta.1
v0.8.2
- Refactoring code to cleanly embed NATS and credentials to create client connections.
- New authentication method support via user_name and user_password fields (for plain text). After NKey this will be second form of authentication, yet to follow up with JWT methodology.
- Included examples folder for quick start demo.
v0.8.2-beta
Refactoring code to cleanly embed NATS and credntials to create client
connections. New authentication method support via user_name and
user_password fields (for plain text). After NKey this will be second
form of authentication, yet to follow up with JWT methodology.
v0.8.1
This version introduces fixes to embedded NATS bootup process that will allow
Marmot processes to wait for streams to be ready before it can proceed
with boot process. This will prevent panic exit from the process and
let individual Marmot processes to come up forming a JS cluster.
v0.8.0
Major feature
Starting 0.8.0
NATS is embedded into Marmot. This will smaller environments to just spin up Marmot nodes without additional overhead of running separate NATS binary.
What's Changed
- Support for Embedded NATS by @maxpert in #43
- Added nkey authentication support by @nclv in #45
- Multi-PK were causing issues by @maxpert in #51
New Contributors
Full Changelog: v0.7.5...v0.8.0
v0.8.0-beta.2
v0.8.0-beta.1
Update README.md
v0.7.5
v0.7.4
v0.7.3
New configurations added to allow finer grain control of Marmot
- publish (to enable/disable publishing of changes locally)
- replicate (to enable/disable replicating changes locally)
- scan_max_changes (Number of maximum rows to process per change allows configuring the maximum number of rows Marmot will process (scan/load in memory) before publishing to NATS)
- cleanup_interval (Cleanup interval in seconds used to clean up published rows. This is done in order to reduce write load on the system)