Torrust-Actix v3.2.1 Patch Fix

Bumped versions, applied security patch, and fixed a bug in the PostgreSQL corner (thanks Babico for notifying about it).

Torrust-Actix v3.2.0

New release of Torrust-Axum tracker, now renamed to Torrust-Actix for switching to a different web framework.
All the changes will be pointed here.

• Bumped library versions.
• Modified the way scheduling was done through threads, it could lock up and slow down public trackers with heavy activity.
• Tweaking the SQLite3 database usage and database space consumption.
• Full overhaul on how torrents and peers are used in memory. Using crossbeam skipmap for thread safe non-locking memory sharing.
• Some various improvement on coding performance, readability and linting the files.
• Replaced Tokio Axum web framework for Actix, reason: Missing critical things like a timeout on connect, disconnect, read and write, and support was lackluster.
• Renamed the github repository from torrust-axum to torrust-actix.
• Adding user tracking support with an extra key.

Torrust-Axum v3.1.2

New release available, bumped versions of libaries with new changes.

• Toggle maintenance mode through API and WebGUI
• Bug fixes

Torrust-Axum v3.1.1 (Update)

Fixed a lot of problems I found out after v3.1.0 release.
The fixes are:

• Database for SQLite3, MySQL and PostgreSQL now works properly with all the tables, and will be used if enabled.
• UDP had a problem in IPv4, fixed the code for correctly parsing byte array.
• Cleanup and refactoring of some redundant code.
• Added some small checks where needed to prevent errors.

Torrust-Axum v3.1.0

New Torrust-Axum release version done.
This version is production ready, and has some exploit fixes applied to it.

The new features for this version are:

• Whitelist System: You can enable this to only allow torrent hashes to be used you specify in the database, or add them through the API.
• Blacklist System: You can enable this to disallow torrent hashes to be used you specify in the database, or add them through the API.
• Keys System: You can enable this to only allow tracking when a activated "key" hash (same as an info_hash, 20 bytes or 40 characters hex) is given. Keys with a timeout of zero "0" will be permanent and won't be purged by the cleanup.
• WebGUI: The API has an available web interface, which can be accessed through https://your.api:8080/webgui/ and giving the correct API Key, which you configurate in the configuration file.
• Customizable database structure can be given in the configuration file.
• The system is also now available through Docker Hub at https://hub.docker.com/r/power2all/torrust-axum

Torrust-Axum v3.0.1

Torrust-Axum is now released as a working project.
It's production ready, as far as I'm using it right now.

Torrust-Axum can run with or without a persistency database as alternative for OpenTracker and other public tracker software.
Private Tracking using a Whitelist and Blacklist will be implemented for version 3.1.0

Torrust-Axum supports:

• SQLite3
• MySQL
• PostgreSQL

Torrust-Axum v3.0.0 (Non-Persistent and MySQL Only)

This is a simple release with 2 binaries pre-compiled (Release and Debug), with a MySQL structure you can use.
Simply, start the binary ones to make it generate a default config.toml file, modify it to your needs, and run the system.
You don't need MySQL, by disabling persistency, but you can use MySQL for persistency saving.

A more enhanced README will be made later, SQLite3 and PostgreSQL support will be also added on a new release version.
For now, you can use this as a alternative to OpenTracker.

A actively used version of Torrust-Axum, can be found at https://www.gbitt.info/