Bitmagnet Versions Save

What's Changed

• Use torrent_content.info_hash instead of torrent_content.id in Torznab result by @mgdigital in https://github.com/bitmagnet-io/bitmagnet/pull/30
• Add nil check by @mgdigital in https://github.com/bitmagnet-io/bitmagnet/pull/31
• Fix error message re: meta info from any pers by @NiklasBr in https://github.com/bitmagnet-io/bitmagnet/pull/34
• docker-compose is deprecated, use docker compose by @NiklasBr in https://github.com/bitmagnet-io/bitmagnet/pull/32
• Update issue templates by @mgdigital in https://github.com/bitmagnet-io/bitmagnet/pull/33

New Contributors

• @NiklasBr made their first contribution in https://github.com/bitmagnet-io/bitmagnet/pull/34

Full Changelog: https://github.com/bitmagnet-io/bitmagnet/compare/v0.0.6...v0.0.7

What's Changed

• Update docsite (#13) by @mgdigital in https://github.com/bitmagnet-io/bitmagnet/pull/16
• Implement multiplatform builds (#18) by @mgdigital in https://github.com/bitmagnet-io/bitmagnet/pull/20
• parsing uint from env variable by @myyc in https://github.com/bitmagnet-io/bitmagnet/pull/26

New Contributors

• @myyc made their first contribution in https://github.com/bitmagnet-io/bitmagnet/pull/26

Full Changelog: https://github.com/bitmagnet-io/bitmagnet/commits/v0.0.6

What's Changed

• Implement multiplatform builds by @Thanzex in https://github.com/bitmagnet-io/bitmagnet/pull/18

New Contributors

• @Thanzex made their first contribution in https://github.com/bitmagnet-io/bitmagnet/pull/18

Full Changelog: https://github.com/bitmagnet-io/bitmagnet/commits/v0.0.5

What's Changed

• Fix importer by @mgdigital in https://github.com/bitmagnet-io/bitmagnet/pull/12

Full Changelog: https://github.com/bitmagnet-io/bitmagnet/compare/v0.0.3...v0.0.4

What's Changed

• Fix: Add equal sign to keys options in docker-compose files by @mgdigital in https://github.com/bitmagnet-io/bitmagnet/pull/7
• Move docker-compose comment to separate line by @mgdigital in https://github.com/bitmagnet-io/bitmagnet/pull/8
• Add files_status field and dht_crawler.save_files_threshold configuration parameter by @mgdigital in https://github.com/bitmagnet-io/bitmagnet/pull/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 torrent
• single: The torrent is a single file and there are no associated file records
• multi: There are one or more files associated with the torrent in the torrent_files table
• over_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: https://github.com/bitmagnet-io/bitmagnet/compare/v0.0.2...v0.0.3

What's Changed

• Add CodeQL workflow by @mgdigital in https://github.com/bitmagnet-io/bitmagnet/pull/3
• Add bounds check to year conversion by @mgdigital in https://github.com/bitmagnet-io/bitmagnet/pull/4
• Add dht_crawler.save_files option; update docs by @mgdigital in https://github.com/bitmagnet-io/bitmagnet/pull/5

Full Changelog: https://github.com/bitmagnet-io/bitmagnet/commits/v0.0.2