1.5.0 release - webtorrent, Heroku, NPM package

Summary

• Replaced torrent-stream with webtorrent - it has a larger community, better performance & updated dependencies.
• Heroku deployment is working now #6!
• Added postinstall command, which will install frontend on every backend install.
• Removed lib / build directories, build command now builds both frontend & backend.
• Backend code refactoring.
• New Github action to publish NPM package on each release.

1.4.0 release - docker, swagger, UI improvements

Github actions & Docker containers

Dockers now rebuild everything from the source (previously it used prebuild code). It allowed to use Github actions: now we have docker container with latest version, which is deployed after each commit to master.

Swagger

Swagger is an Interface Description Language for describing RESTful APIs expressed using JSON/YAML.

It let's us do following:

• Generate API configuration - preview
• Generate typescript frontend client (frontend/src/helpers/client)
• Generate backend models (src/models)

UI improvements

Browse page

Small visual improvements + added more data, like a link to the torrent, labels, etc.

Play page

The play page now supports images, text files & videos.

Other improvements

• Added prettier
• Added editorconfig
• Refactoring & code improvements

1.3.0 - browse torrents

Browse torrents

The new browse page lets you browse torrents from different providers & categories.

At the moment two providers are supported:

1. ThePirateBay using apibay.org
2. Nyaa.si using Nyaapi

Other improvements

We got our first pull request from pataquets which adds direct stream/download links for files.

Future plans

More torrent providers

I am planning to add more torrent providers. Create a new request if you wish your favorite provider to be included on the browse page!

Better browse page

Different providers have different features. Some have some kind of special filters (like VIP), some support pagination, some show download counts. I wish to add all these features to the browse page and show if the provider supports it.

1.2.1 - improvements & fixes

Summary

• Ability to change app host.
• Fixed startup message which displayed an incorrect host.
• Behind proxy support for IP detection.

1.2.0 - small improvements

Summary

• Demo page stores the latest torrents in local storage for each user and shows up to 10 history items on the home page.
• Previously only torrent magnet links were supported, now you can use torrent file URL.
• Better error handling, fixed hanging issues while encountering API errors.
• Better deployment (Heroku & google apps) support

1.1.2 - bug fix #2

Bug Fixes

• Fixed demo page query parameter encoding

1.1.1 - bug fix

Bug Fixes

• In previous release demo page used file path, but stream compared file names - so when path and name were different, stream returned the first file.

Improvements

• Stream now supports either full file path or file name (you can pass it to file query parameter).
• Stream returns content-type header.
• Stream returns content-disposition header with the file name.

1.1.0 - new demo page

New demo page

Choose which file to stream

A lot of torrents have multiple files in one torrent. The previous demo played the first file, now you can choose which to play.

Usage dashboard

In one dashboard you can monitor what at the moment the server is streaming and how much free space you have.

API remake

Because the new demo uses only API, I needed a lot of new API features. So basically old API endpoints changed somehow (well, except steam API - it is still the same).

Check more in readme.

Api protection

Because now API has to write access (you can create a new torrent using API) - you can set API key in config. Demo page also supports API key which you need to enter in the popup. You will need to reenter the key after each page reload - so it's recommended to save it to the password manager.