add-torrent

Send magnet links or torrent URLs to a remote Transmission daemon in your browser or via HTTP.

Configuration

Set the following environment variables:

$TRANSMISSION_RPC_URL: URL of your Transmission daemon's RPC interface, defaults to http://localhost:9091/transmission/rpc/.
$DOWNLOAD_DIRECTORIES: array of name:/my/directory,… for torrent content to be moved to upon completion.
$PORT: to serve from, defaults to 3000.

Usage

npm install
npm start

and open http://localhost:3000/.

Command Line

Using httpie:

http post localhost:3000/ url='https://archive.org/download/flickr-ows-05-6503285175/flickr-ows-05-6503285175_archive.torrent'
# HTTP/1.1 201 Created
# Content-Type: application/json; charset=utf-8
# …
# ETag: 02234f9cb44ba1157473578ccc94cbbbb3be04fa
#
# {
#     "hashString": "02234f9cb44ba1157473578ccc94cbbbb3be04fa",
#     "id": 626,
#     "name": "flickr-ows-05-6503285175",
#     "url": "https://archive.org/download/flickr-ows-05-6503285175/flickr-ows-05-6503285175_archive.torrent"
# }

Build

Via Docker:

docker build -t $DOCKER_USERNAME/add-torrent .

Deploy

Kubernetes via Helm

Check values.yaml for full list of settings:

cd helm
helm install add-torrent \
    --set transmissionRpcUrl=$TRANSMISSION_RPC_URL \
    # see <https://github.com/kubernetes/helm/blob/master/docs/using_helm.md#the-format-and-limitations-of---set>
    --set downloadDirectories=$(echo $DOWNLOAD_DIRECTORIES | sed 's/,/\\\,/g') \
    # use NodePort for minikube, ClusterIP for ingress-nginx, otherwise LoadBalancer
    --set service.type=NodePort

For production use with an existing ingress-nginx configuration:

helm install add-torrent \
    --set transmissionRpcUrl=$TRANSMISSION_RPC_URL \
    --set downloadDirectories=$(echo $DOWNLOAD_DIRECTORIES | sed 's/,/\\\,/g') \
    --set ingress.enabled=true \
    --set ingress.hosts="{my.host.name,}"

jeffbr13 / add-torrent