
Two big new features:
- Full IP support (built-in regex, ip ranges, different actions on IPv4 and IPv6...)
- Options for action deduplication
See the release for a more detailed changelog:
https://framagit.org/ppom/reaction/-/releases/v2.2.0
Two big new features:
- Full IP support (built-in regex, ip ranges, different actions on IPv4 and IPv6...)
- Options for action deduplication
See the release for a more detailed changelog:
https://framagit.org/ppom/reaction/-/releases/v2.2.0
Two big new features:
- Full IP support (built-in regex, ip ranges, different actions on IPv4 and IPv6...)
- Options for action deduplication
See the release for a more detailed changelog:
https://framagit.org/ppom/reaction/-/releases/v2.2.0
For the needs of #reaction, I wrote a very dumb #Rust#KV db which wraps BTreeMaps and a redis-like log file for persistance.
It's orders of magnitude faster than common KV #database (heed/lmdb, fjall, sled) because it's RAM-first.
But it doesn't have transactions, and it persists write operations asynchronously, after the write is done.
Those features make a lot of sense for reaction imo, but I don't know if it would be useful to others.
Question is: should I publish it as a separate crate?
For the needs of #reaction, I wrote a very dumb #Rust#KV db which wraps BTreeMaps and a redis-like log file for persistance.
It's orders of magnitude faster than common KV #database (heed/lmdb, fjall, sled) because it's RAM-first.
But it doesn't have transactions, and it persists write operations asynchronously, after the write is done.
Those features make a lot of sense for reaction imo, but I don't know if it would be useful to others.
Question is: should I publish it as a separate crate?
This is a more stable release than previous rc.
Admins are encouraged beta-test it before the first stable v2!
https://framagit.org/ppom/reaction/-/releases/v2.0.0-rc2
#reaction #rust #release
A space for Bonfire maintainers and contributors to communicate