sparklyballs

oh, and the update is ready. look at the other thing regards the webui tomorrow, watching a movie.

the old container was pulling the latest git commit, this one is pulling the latest release.

K, autotools loading torrents watched folder is working now. fixed the perms on the nginx tmp folder made the php.ini file user-editable in /config/php gonna push the PR to the main repo now. i'll let you know when the build is pushed to the hub. also put a commented out line in the rtorrent.rc for watch folder enabling.

it's currently 20:21 in the uk, so you can see how recent this is...

if that helps Another similar issue http://forums.rutorrent.org/index.php?PHPSESSID=462ee4f8afb81093d2c735f62a52fe61&topic=288.msg1729#msg1729 i had no issue with rss feeds in testing, there is no folder plugins/rss/cache problem with most information for this "lovely" software, it's woefully out of date, lol.

take the tilde "~" out and it's watched schedule = watch_directory_1,5,5,"load.start=/downloads/watched/*.torrent" I suppose I understand the tilde, but why "watched"? I specifically created a folder called watch. that said, made the change and HOT DAMN it worked. [sigh] ... now I need to get it to remove the torrent file, but that is my problem to deal with Have you made the permission change? Should I kill and download the docker image / container? The autowatch tools are indeed easier to deal with from the GUI of course I'm building a test copy on my VM at the moment, takes a little while as have to compile one of the dependencies from source.

sorry if that is opaque, I'm trying to track down the issue with autowatch. that is another one of the "things to check" from here http://forums.rutorrent.org/index.php?PHPSESSID=557b64757da258035d65eb80f2a4ad26&topic=645.msg4895#msg4895 changing the config in question to on and placing a torrent for ubuntu server iso in the watched folder and waiting about 10 minutes or so it started downloading.

take the tilde "~" out and it's watched schedule = watch_directory_1,5,5,"load.start=/downloads/watched/*.torrent"

let's deal with this one first, it's the easiest, lol. seems there's a file size limit beyond which it writes to the tmp folder for nginx, i guess the torrents i was testing with were below the file limit. I'm adding a perms fix to that folder.

sorry if that is opaque, I'm trying to track down the issue with autowatch. that is another one of the "things to check" from here http://forums.rutorrent.org/index.php?PHPSESSID=557b64757da258035d65eb80f2a4ad26&topic=645.msg4895#msg4895 the file in question for php.ini is /etc/php7/php.ini currently "register_argc_argv = Off" is the setting. and /usr/bin/php7 is the correct path. if you can confirm that setting register_argc_argv = On enables autotools, i'll sed it in to the dockerfile or one of the startup init files.

No worries.

Let me know when the donations page is working again. Donations page is live sir Donation sent. Thanks for everything. Thank you very much for your generous donation, that will most certanly help us out and is greatly appreciated.

from unraid command line type. ls -lah /mnt/user and paste the output here.

Image has been rebased to alpine linux, as part of the change the config folder structure has been modified and the recommended upgrade method is to clear appdata and reinstall. For more information on the changes from linuxserver.io see. http://lime-technology.com/forum/index.php?topic=50793

We are phasing in new image updates gradually rather than all at once. https://github.com/linuxserver/docker-rutorrent/pull/8 is the relevant PR for rutorrent. the config folder structure has been reorganised a little and the recommended update path will be a crash and burn of config.

Haha, fair enough I shall have to get round to that next week then Do you reckon I'd have to do that every time the docker is updated? Or just this once to 'fix' something that's gone wonky? The files of the app itself are stored outside the container. So i'd say everytime the app itself is updated at this stage.

My old eyes never noticed the version number, revisiting it, it seems the best way to update is to crash and burn.

Image has been rebased to alpine linux, also fixed issue with keypair data not being persistent, first update to new baseimage will still require keypair data to be reentered, but from then on it should be persistent. For more information on the changes from linuxserver.io, see. http://lime-technology.com/forum/index.php?topic=50793

Image has been rebased to ubuntu xenial and the app itself updated to 2.12. More info on changes at linuxserver.io http://lime-technology.com/forum/index.php?topic=50793

Sonarr has been rebased to use xenial ubuntu with s6 overlay, part of the image update is the dropping of autoupdates by restarting the container. More details on changes from linuxserver.io team. http://lime-technology.com/forum/index.php?topic=50793.0

Image has been rebased to alpine linux and as part of that more config options have been made available in /config. Also should be noted that the url for the webui has been changed to /smokeping/smokeping.cgi

Just add an extra path in the docker webui on Unraid. Edit the container config and do it there. unfortunately even when i do add the path when trying to edit autotools to use this folder its stuck in the download folder? any changes made in the webui are not permanent and only apply to that session, ie until the docker is restarted. this is a limitation of the apps themselves https://github.com/Novik/ruTorrent/wiki#some-non-obvious-points any permanent changes need to be made to the rtorrrent.rc file /config/rtorrent/rtorrent.rc

i'd go with putting it after mono in the line.

to modify the startup settings for sonarr , exec into the container docker exec -it <container-name> bash and modify the file /etc/service/sonarr/run exit out and restart the container docker restart <container-name>

update the docker from the docker pane in unraid webui, to get on to the 1.x version.