Releases: bitmagnet-io/bitmagnet
v0.3.0
What's Changed
- Add deletion functionality in API and web UI by @mgdigital in #75
- Add torrent tagging in API and WebUI by @mgdigital in #60
- Add refresh button to web UI by @mgdigital in #73
- Add name and size attributes to magnet links by @mgdigital in #72
- Add database indexes improving search performance by @mgdigital in #74
- Reduce frequency of crawler database queries (should improve API and web UI performance) by @mgdigital in #79
- Add client suffix to DHT node ID by @mgdigital in #77
- Add Discord link to web UI by @mgdigital in #78
- Bump @babel/traverse from 7.22.17 to 7.23.2 in /webui by @dependabot in #41
New Contributors
- @dependabot made their first contribution in #41
Full Changelog: v0.2.0...v0.3.0
v0.2.0
What's Changed
- Observability enhancements by @mgdigital in #67
This release is about improving observability:
- Clean up logging and reduce verbosity of debug level
- Add optional logging to rotated files
- Add prometheus metrics endpoint
- Add pprof profiling endpoint
- Add asynqmon monitoring web UI
- Add example configurations for Grafana, Prometheus, Loki, Pyroscope
- Dial down the concurrency/buffering in parts of the crawler pipeline which was a bit too high by default
- Some refactoring in places to decouple things and avoid munging implementations with the prometheus collector and logging
See https://bitmagnet.io/internals-development/observability-telemetry.html
Full Changelog: v0.1.1...v0.2.0
v0.1.1
What's Changed
- Update docsite by @mgdigital in #48
- Fix config resolver bug by @mgdigital in #61
- Respect savePieces config by @mgdigital in #62
The DHT crawler was incorrectly saving pieces which may use a lot of database disk space. To recover the used space you'll need to run the following query on the Postgres database (this may take a few minutes):
update torrents set pieces = null, piece_length = null where pieces is not null;
Full Changelog: v0.1.0...v0.1.1
v0.1.0
What's Changed
- when tmdb found and adult movie we set the type xxx by @dr4gn3l in #44
- Address #11 with BEP5 & BEP51 implementations
- Reimplement DHT crawler around new routing table
- Fix #45
- Fix #42
- Fix #39
- Fix #37
- Make bootstrap nodes configurable: #27
- Add profiling tools to Docker image
- Add checkers to reject crawled torrents based on criteria by @mgdigital in #46
New Contributors
Full Changelog: v0.0.7...v0.1.0
v0.0.7
What's Changed
- Use torrent_content.info_hash instead of torrent_content.id in Torznab result by @mgdigital in #30
- Add nil check by @mgdigital in #31
- Fix error message re: meta info from any pers by @NiklasBr in #34
docker-compose
is deprecated, usedocker compose
by @NiklasBr in #32- Update issue templates by @mgdigital in #33
New Contributors
Full Changelog: v0.0.6...v0.0.7
v0.0.6
What's Changed
- Update docsite (#13) by @mgdigital in #16
- Implement multiplatform builds (#18) by @mgdigital in #20
- parsing uint from env variable by @myyc in #26
New Contributors
Full Changelog: https://github.com/bitmagnet-io/bitmagnet/commits/v0.0.6
v0.0.5
v0.0.4
v0.0.3
What's Changed
- Fix: Add equal sign to keys options in docker-compose files by @mgdigital in #7
- Move docker-compose comment to separate line by @mgdigital in #8
- Add files_status field and dht_crawler.save_files_threshold configuration parameter by @mgdigital in #9
Notes on files optimisations
Some torrents contain many thousands of files, which impacts performance and uses a lot of database disk space.
This update adds more control over saving of file information for torrents.
It adds the configuration parameter dht_crawler.save_files_threshold
(default 50
) over which file info for a torrent will not be saved.
It contains a database migration which adds a files_status field to the torrents table. This can be:
no_info
: We don't know anything about the files in this torrentsingle
: The torrent is a single file and there are no associated file recordsmulti
: There are one or more files associated with the torrent in thetorrent_files
tableover_threshold
: File information was not saved because the number of files was over the configured threshold
After the migration has been run, anyone wanting to clean there database of torrents with too many files can run the query:
delete from torrents where torrents.files_status = 'multi' and (select count(*) from torrent_files where torrent_files.info_hash = torrents.info_hash) > 50
Full Changelog: v0.0.2...v0.0.3
v0.0.2
What's Changed
- Add CodeQL workflow by @mgdigital in #3
- Add bounds check to year conversion by @mgdigital in #4
- Add dht_crawler.save_files option; update docs by @mgdigital in #5
Full Changelog: https://github.com/bitmagnet-io/bitmagnet/commits/v0.0.2