What's Changed

• Hot Fix for the redis/memcache system, instead of having a persistent connection, only connect when needed
• Updated the readme for some information how to use the Cache system

Full Changelog: v4.2.5...v4.2.6

What's Changed

• Preparing v4.2.5 with Cache fixes and bumping a library (lz4_flex) th… by @Power2All in #72
• Fixing tests by @Power2All in #73

Full Changelog: v4.2.4...v4.2.5

What's Changed

• Fixing a SSL bug I just discovered, multiple SSL/TLS providers, need … by @Power2All in #71

Full Changelog: v4.2.3...v4.2.4

What's Changed

• Bug-fix the peers reaping by @Power2All in #70

Full Changelog: v4.2.2...v4.2.3

What's Changed

• v4.2.2 by @Power2All in #69

Full Changelog: v4.2.1...v4.2.2

What's Changed

• Adding LZ4/ZSTD compression for memory objects for the RtcTorrent peer data, enabled by default, disablable through config
• Memory optimization for the peer data
• Some small bug fixes

Full Changelog: v4.2.0...v4.2.1

What's Changed

• Refactoring the whole project structure
• Adding security and anti-malicious validation and checks
• Adding RtcTorrent library and support to the tracker, for web streaming and downloading of BitTorrent. This is a major change from v4.1.0. It uses the default HTTP BitTorrent announce endpoint, with additional parameters
• Fixed IPv4/IPv6 pool system for better support for clients and seeders.

Full Changelog: v4.1.1...v4.2.0

• Added hot reloading of SSL certificates for renewal
• API has an extra endpoint to run the hot reloading
• Some more code optimizations

Biggest release, introducing Clustering, UDP Simple Proxy Protocol (Cloudflare technique), database code improvement, Redis and Memcache caching (active peer data), and many other code enhancements.

• Added a full Cluster first version through WebSockets
• Option to run the app in Stand-Alone (which is default, as single server), or using the cluster mode
• When set to Master, it still functions as if being Stand-Alone, but with WebSocket support for clustering
• When set to Slave, it will forward all the requests to the Master server to be handled
• Added configurations to be applied in config.toml and the environment variables
• Added statistics, also showing cluster statistics next to the rest. Slave will only show active requests
• WebSocket data can be sent in 3 different ways, but Master server is the leading what way to talk
• This is a very early version of the WebSocket cluster implementation, and needs thorough testing
• Moved the more database engines additions to another version (and MeiliSearch/ElasticSearch support for v4.2)
• Refactored the database engine to be less massive, more logical and less redundancy
• Implemented a Redis and Memcache cache optionally to push peer data to, for usage on websites (without burdening SQL)
• Added UDP support for Cloudflare's "Simple Proxy Protocol" (https://developers.cloudflare.com/spectrum/how-to/enable-proxy-protocol/#enable-simple-proxy-protocol-for-udp)

Be warned, the config.toml and Environment variables have been extended.
The plan is, when we need to introduce new config variables, we will introduce also a new minor version.
Before you update to this version, use torrust-actix --create-config to generate a new configuration file, or check the errors of variable keys missing. You can also check the README.MD file for the new environment key names.

I strongly advice to update to this version, cause of performance tweaks and significant enhancements.

This will possibly the last release for the 4.0 branch.
I've decided, when a extreme change comes in the future (like config file changes), a new minor version will be applied.
Should have done this when I started updating UDP config file block to 4.1, but alas, I learn from my mistakes.

• Another little overhaul, changing some memory tools for enhancement and performance
• Less CPU cycles applied when requests are handled
• Preparing for v4.1 to add some more database engines to the mix apart from SQLx