...
Code Block | ||
---|---|---|
| ||
L_KEY="[KEY]"
L_HOST="tracker.someserver.net"
L_TRACKERPROXYURL="https://tracker.someserver.net:443/tracker/uannounce"
L_TRACKERPROXYLISTEN="localhost:8080"
L_URLS="https://tracker.someserver.net/torrent/all.json ... ..."
|
L_URLS is a set of STOMP destinations and/or RSS feeds. Each destination is pulled regularly and each link is downloaded. If the downloaded data is a BitTorrent file it is stored in the --torrentDir
directory and added to transmission.
By default (L_STDNOTIFY="True") the standalone storage node will listen to stomp://tracker.someserver.net/torrent/new.
STOMP destinations
Location | What it gets you |
---|---|
/torrent/new | Each newly created torrent |
/torrent/tag/add | Each time a torrent is tagged |
/torrent/tag/add/foo | Each time a torrent is tagged with 'foo' |
/torrent/tag/remove/foo | Each time the 'foo' tag is removed from a torrrent |
RSS URLs
Location | What it gets you |
---|---|
https://lobber.example.org/torrents/all.rss | All torrents readable by the current user (or key) |
https://lobber.example.org/torrents/tag/foo.rss | All torrents tagged with 'foo' |
Copy the script to the start up script folder and change permissions on it.
...
Code Block |
---|
/etc/init.d/lobberstoragenode webapp start |
Unrevised old documentation
When running a storage-node for development purposes you will typically run it with both the --stompUrl
and --lobberUrl
parameters pointing to endpoints on your local development sandbox. When running a storage-node off of beta.lobber.se
you will typically want to start it this way:
Code Block |
---|
# twistd -n lobberstoragenode -k <appkey> -h beta.lobber.se -d /var/torrents [<destination|rss>]*
|
The final arguments is a set of STOMP destinations and/or RSS feeds. Each RSS feed is pulled regularly and each link is downloaded. If the downloaded data is a BitTorrent file it is stored in the --torrentDir
directory (/var/torrents
in the example above). Optionally if a --script
option was given it will be run as a command with the path to the torrent-file as an argument.
If you want to notify transmission of new torrents you might do something like this
Code Block |
---|
# twistd -n lobberstoragenode ... --script="transmission-remote -n transmission:transmission -a"
|
A more complete example. This would regularly pull all torrents linked from https://beta.lobber.se/torrent/tag/foo.rss
and ask transmission to add the new ones.
Code Block |
---|
# twistd -n lobberstoragenode -k <key> -h beta.lobber.se -d /tmp \\
--script="transmission-remote -n transmission:transmission -a" \\
https://beta.lobber.se/torrent/tag/foo.rss /torrent/tag/foo
|
Useful stuff to listen to for a storagenode
STOMP destinations
Location | What it gets you |
---|---|
/torrent/new | Each newly created torrent |
/torrent/tag/add | Each time a torrent is tagged |
/torrent/tag/add/foo | Each time a torrent is tagged with 'foo' |
/torrent/tag/remove/foo | Each time the 'foo' tag is removed from a torrrent |
RSS URLs
...
Location
...
What it gets you
...
https://lobber.example.org/torrents/all.rss
...
All torrents readable by the current user (or key)
...
https://lobber.example.org/torrents/tag/foo.rss
...