Skip to content

v2.2.0

Latest

Choose a tag to compare

@vintikzzz vintikzzz released this 18 Nov 06:44
0ce3099

Before you upgrade

  • External S3 (USE_LOCALS3=false with AWS_ENDPOINT): create the torrent-store bucket there, or set TORRENT_STORE_AWS_BUCKET to a bucket you already have, before you start the new image. torrent-store now writes every added torrent to that bucket first, so while the bucket is missing or not writable, adding torrents fails. The built-in store and instances without S3 need nothing.
  • Private torrents: set PRIVATE_TRACKERS_KEY (64 hex digits, for example openssl rand -hex 32) and pass the same value on every later docker run. Without it a key is generated inside the container, and recreating the container (every upgrade) makes the stored tracker records unreadable.
  • web-ui applies new database migrations on start, and there is no way back to the old schema. Back up your data volume first if you may want to return to v2.1.2.

What's new

  • Private torrents. A .torrent with the private flag plays through its tracker under the account that uploaded it. The tracker URLs, passkey included, are kept per account, encrypted, in the torrent-store bucket; another account is refused until it uploads the .torrent itself. Needs accounts and S3, see Private torrents. PRIVATE_ACCESS_ENFORCE (default false) only counts refusals for now, so private torrents added before this release keep playing.
  • AI subtitles turn on with either AI key.
  • arm64: video-info is pinned to its multi-arch image; the arm64 images of v2.1.0–v2.1.2 carried an amd64 build of it.
  • external-proxy: EXTERNAL_PROXY_PRIVATE_NETWORK_ORIGINS lists the origins posters and subtitles may be fetched from at a private address; your own DOMAIN is always on the list.
  • README: embeds are served by your own instance, and the embed domain list is not access control.
  • Component images updated.