July 7, 201510 yr I see that you guys created individual support threads for most of your containers. What you really should also do is add the <Support> line to the templates pointing that container to its particular thread I'll get to that! Only just made them, gimme a chance! no problems. Just didn't know if you were aware of that line or not <Support> tag line now added to our templates
July 7, 201510 yr Author And now i have to pay attention to 10 support threads instead of 1 With notifications why does it matter? And the users have asked for it, so we should oblige.
July 7, 201510 yr a quick google shows that you can use ssmtp with smokeping and it's fairly easy to use in a container. We always welcome contributors, fork it on Github and send us a pull when you're done. Oh and join us on IRC freenode #linuxserver.io to discuss specifics if you wish. done... also inadvertantly fixed up the permissions errors too. that user init script needs to be first to run otherwise any chown's in init files prior to it running will have the original uid and gid for abc.
July 7, 201510 yr Hi, everyone. I would just like to say we do take requests and another major difference here is that these containers anyone is suggested to contribute too. Also I approve this thread Figured I would throw this out there if you take requests, PlexEmail. This would be an excellent addition to unRAID. https://github.com/jakewaldron/PlexEmail and when Plex's forums are back online: https://forums.plex.tv/index.php/topic/151619-plexemail-in-development/
July 7, 201510 yr ironicbadger, You mention that all the dockers are auto-updated on restart of the docker. Is this the case with the Plex app as well? I noticed over at linuxserver.io lonix mentions this in his container notes which isn't really "auto updated" "Autoupdate, requires lonix to update a file on a webserver" Mainly just wondering because I was thinking about giving it a try from needo's, however needos "really" auto-updates.
July 7, 201510 yr Thank for the containers, I've replaced all my existing usenet tools with yours. Also, you might want to add a direct link to your repo for those that aren't using the Community Applications plugin.
July 7, 201510 yr Thank for the containers, I've replaced all my existing usenet tools with yours. Also, you might want to add a direct link to your repo for those that aren't using the Community Applications plugin. Repo address is also listed in the Popular Repositories thread.
July 7, 201510 yr Author ironicbadger, You mention that all the dockers are auto-updated on restart of the docker. Is this the case with the Plex app as well? I noticed over at linuxserver.io lonix mentions this in his container notes which isn't really "auto updated" "Autoupdate, requires lonix to update a file on a webserver" Mainly just wondering because I was thinking about giving it a try from needo's, however needos "really" auto-updates. What we meant was that the plex app updates on container restart. We (both lonix and I) update the file in question within 4 hours max of a plex release but usually a lot less. All the user need do is restart the container. Now, the issue with plex specifically is the handling of auto update for plexpass. It's not easily possible to automate that yet but the not pass version is easy with relying on a third party service (baconater) like he does I think.
July 7, 201510 yr "Are you sure the /downloads folder is owned by the correct user now ? Try this: Code: [select] chown -R 99:100 /home/docker/volumes/downloads && rm /home/docker/volumes/downloads/nzbget.lock" Thanks for the help...I did chown the folders, but if i kill, remove and re-pull and the container the permissions go back...one of the scripts must change the permissions upon building. I will wait to use this until docker until that is worked out... Thanks again for the help!
July 7, 201510 yr ironicbadger, You mention that all the dockers are auto-updated on restart of the docker. Is this the case with the Plex app as well? I noticed over at linuxserver.io lonix mentions this in his container notes which isn't really "auto updated" "Autoupdate, requires lonix to update a file on a webserver" Mainly just wondering because I was thinking about giving it a try from needo's, however needos "really" auto-updates. What we meant was that the plex app updates on container restart. We (both lonix and I) update the file in question within 4 hours max of a plex release but usually a lot less. All the user need do is restart the container. Now, the issue with plex specifically is the handling of auto update for plexpass. It's not easily possible to automate that yet but the not pass version is easy with relying on a third party service (baconater) like he does I think. thanks, ya I knew you meant on restart, but its not "automated" to say if you decide to hightail it out of here (not saying you will, just making the point). I assume the issue is the random string plex passes in the URL for each release?? https://downloads.plex.tv/plex-media-server/0.9.12.4.1192-8a45d21/PlexMediaServer-0.9.12.4.1192-8a45d21-x64-UnRAID.txz
July 8, 201510 yr Howdy all. Ironic, nice to see you back frequenting the forums. Since you're taking requests, I'd love to make a request for sabnzbd (with multicore par2!!). I know there are lots of sabnzbd dockers out there already, but none seem to allow me to pull down alpha/beta/RC versions. This would be stellar, and then I could run my other 2 containers (CP and Sonarr) all under a unified base image. Sounds like bliss to me. Thanks in advance! If not possible, no worries.
July 8, 201510 yr Author Howdy all. Ironic, nice to see you back frequenting the forums. Since you're taking requests, I'd love to make a request for sabnzbd (with multicore par2!!). I know there are lots of sabnzbd dockers out there already, but none seem to allow me to pull down alpha/beta/RC versions. This would be stellar, and then I could run my other 2 containers (CP and Sonarr) all under a unified base image. Sounds like bliss to me. Thanks in advance! If not possible, no worries. Easy, we already have a Sab image that lonix made. Can convert it to be an alpha/beta friendly version I'm sure.
July 8, 201510 yr Howdy all. Ironic, nice to see you back frequenting the forums. Since you're taking requests, I'd love to make a request for sabnzbd (with multicore par2!!). I know there are lots of sabnzbd dockers out there already, but none seem to allow me to pull down alpha/beta/RC versions. This would be stellar, and then I could run my other 2 containers (CP and Sonarr) all under a unified base image. Sounds like bliss to me. Thanks in advance! If not possible, no worries. Easy, we already have a Sab image that lonix made. Can convert it to be an alpha/beta friendly version I'm sure. Ill add it to my growning todo\wishlist ironicbadger, You mention that all the dockers are auto-updated on restart of the docker. Is this the case with the Plex app as well? I noticed over at linuxserver.io lonix mentions this in his container notes which isn't really "auto updated" "Autoupdate, requires lonix to update a file on a webserver" Mainly just wondering because I was thinking about giving it a try from needo's, however needos "really" auto-updates. What we meant was that the plex app updates on container restart. We (both lonix and I) update the file in question within 4 hours max of a plex release but usually a lot less. All the user need do is restart the container. Now, the issue with plex specifically is the handling of auto update for plexpass. It's not easily possible to automate that yet but the not pass version is easy with relying on a third party service (baconater) like he does I think. thanks, ya I knew you meant on restart, but its not "automated" to say if you decide to hightail it out of here (not saying you will, just making the point). I assume the issue is the random string plex passes in the URL for each release?? https://downloads.plex.tv/plex-media-server/0.9.12.4.1192-8a45d21/PlexMediaServer-0.9.12.4.1192-8a45d21-x64-UnRAID.txz Yes and No, the "random" string is not random, its the acctual build number. and the real problem is that there is no way to request "latest-plexpass" version from a developing standpoint. we have debated useing baconcode like some other containers have, but im not quite sure im confortable useing that quite yet. so for now. The version number must be updated manually. but it should seem fairly automatic for the user. ( I have been doing it for the last 1.5 years allready. ) and i gave the rest of the lsio crew the chance to do the same. Sorry "Are you sure the /downloads folder is owned by the correct user now ? Try this: Code: [select] chown -R 99:100 /home/docker/volumes/downloads && rm /home/docker/volumes/downloads/nzbget.lock" Thanks for the help...I did chown the folders, but if i kill, remove and re-pull and the container the permissions go back...one of the scripts must change the permissions upon building. I will wait to use this until docker until that is worked out... Thanks again for the help! We have discoverd a issue, i will look in to it, and get back at you soon. Thank for the containers, I've replaced all my existing usenet tools with yours. Also, you might want to add a direct link to your repo for those that aren't using the Community Applications plugin. I Shall commence cicking IB too add said link to OP. a quick google shows that you can use ssmtp with smokeping and it's fairly easy to use in a container. We always welcome contributors, fork it on Github and send us a pull when you're done. Oh and join us on IRC freenode #linuxserver.io to discuss specifics if you wish. done... also inadvertantly fixed up the permissions errors too. that user init script needs to be first to run otherwise any chown's in init files prior to it running will have the original uid and gid for abc. Thanks, i dont undertand how i missed this for so long in so many containers.
July 8, 201510 yr Oh and if if forgot to address your issue here, im sorry i forgot. please ask again under the individual thread here in this forum, Link in OP. (And if you are running non-unraid, please address your issues at the http://linuxserver.io web site.
July 8, 201510 yr Yes and No, the "random" string is not random, its the acctual build number. and the real problem is that there is no way to request "latest-plexpass" version from a developing standpoint. we have debated useing baconcode like some other containers have, but im not quite sure im confortable useing that quite yet. so for now. The version number must be updated manually. but it should seem fairly automatic for the user. ( I have been doing it for the last 1.5 years allready. ) and i gave the rest of the lsio crew the chance to do the same. Sorry thanks and no worries just wondering. I switched over to your sonarr, cp and get and so far so good, all things looking up! thanks for all the hard work! Maybe a thought, but why not make the text file community editable or would that be to big an issue if people start messing with it?
July 8, 201510 yr Yes and No, the "random" string is not random, its the acctual build number. and the real problem is that there is no way to request "latest-plexpass" version from a developing standpoint. we have debated useing baconcode like some other containers have, but im not quite sure im confortable useing that quite yet. so for now. The version number must be updated manually. but it should seem fairly automatic for the user. ( I have been doing it for the last 1.5 years allready. ) and i gave the rest of the lsio crew the chance to do the same. Sorry thanks and no worries just wondering. I switched over to your sonarr, cp and get and so far so good, all things looking up! thanks for all the hard work! Maybe a thought, but why not make the text file community editable or would that be to big an issue if people start messing with it? Actually I pushed a new version a few hours ago that now is automatic. Thanks to my friend Kode whom reasonatly joined lsio
July 8, 201510 yr Howdy all. Ironic, nice to see you back frequenting the forums. Since you're taking requests, I'd love to make a request for sabnzbd (with multicore par2!!). I know there are lots of sabnzbd dockers out there already, but none seem to allow me to pull down alpha/beta/RC versions. This would be stellar, and then I could run my other 2 containers (CP and Sonarr) all under a unified base image. Sounds like bliss to me. Thanks in advance! If not possible, no worries. Easy, we already have a Sab image that lonix made. Can convert it to be an alpha/beta friendly version I'm sure. Ill add it to my growning todo\wishlist ironicbadger, You mention that all the dockers are auto-updated on restart of the docker. Is this the case with the Plex app as well? I noticed over at linuxserver.io lonix mentions this in his container notes which isn't really "auto updated" "Autoupdate, requires lonix to update a file on a webserver" Mainly just wondering because I was thinking about giving it a try from needo's, however needos "really" auto-updates. What we meant was that the plex app updates on container restart. We (both lonix and I) update the file in question within 4 hours max of a plex release but usually a lot less. All the user need do is restart the container. Now, the issue with plex specifically is the handling of auto update for plexpass. It's not easily possible to automate that yet but the not pass version is easy with relying on a third party service (baconater) like he does I think. thanks, ya I knew you meant on restart, but its not "automated" to say if you decide to hightail it out of here (not saying you will, just making the point). I assume the issue is the random string plex passes in the URL for each release?? https://downloads.plex.tv/plex-media-server/0.9.12.4.1192-8a45d21/PlexMediaServer-0.9.12.4.1192-8a45d21-x64-UnRAID.txz Yes and No, the "random" string is not random, its the acctual build number. and the real problem is that there is no way to request "latest-plexpass" version from a developing standpoint. we have debated useing baconcode like some other containers have, but im not quite sure im confortable useing that quite yet. so for now. The version number must be updated manually. but it should seem fairly automatic for the user. ( I have been doing it for the last 1.5 years allready. ) and i gave the rest of the lsio crew the chance to do the same. Sorry "Are you sure the /downloads folder is owned by the correct user now ? Try this: Code: [select] chown -R 99:100 /home/docker/volumes/downloads && rm /home/docker/volumes/downloads/nzbget.lock" Thanks for the help...I did chown the folders, but if i kill, remove and re-pull and the container the permissions go back...one of the scripts must change the permissions upon building. I will wait to use this until docker until that is worked out... Thanks again for the help! We have discoverd a issue, i will look in to it, and get back at you soon. Thank for the containers, I've replaced all my existing usenet tools with yours. Also, you might want to add a direct link to your repo for those that aren't using the Community Applications plugin. I Shall commence cicking IB too add said link to OP. a quick google shows that you can use ssmtp with smokeping and it's fairly easy to use in a container. We always welcome contributors, fork it on Github and send us a pull when you're done. Oh and join us on IRC freenode #linuxserver.io to discuss specifics if you wish. done... also inadvertantly fixed up the permissions errors too. that user init script needs to be first to run otherwise any chown's in init files prior to it running will have the original uid and gid for abc. Thanks, i dont undertand how i missed this for so long in so many containers. because it would only manifest itself on first run or after a save/edit of a container. so in developement you probably wouldn't see it. had something similar with musicbrainz container.
July 8, 201510 yr "We have discoverd a issue, i will look in to it, and get back at you soon. " Good to hear...I look forward to the fix! EDIT: Tested out the new nzbget and it is working now without changing the owner/permissions! Awesome! Also tested out the new plex, but it has a slight issue: *** Running /etc/my_init.d/10_dbus.sh... *** Running /etc/my_init.d/11_new_user.sh... *** Running /etc/my_init.d/20_update_plex.sh... % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 1 100 21 0 0 117 0 --:--:-- --:--:-- --:--:-- 117 *** Running /etc/my_init.d/99_chown_plex_owned_files.sh... find: `/config/Library/Application Support': No such file or directory *** /etc/my_init.d/99_chown_plex_owned_files.sh failed with status 1 It keeps on getting stuck here and repeats until I kill the container... I know all the perms on the config folder are working, so maybe that script is running too soon?? Thanks! Thant should be fixed now.
July 8, 201510 yr For updating to the latest Plex, what about making the "version string" user definable? going to plex.tv one could easily find the current stable or plex-pass version and input it themselves.
July 8, 201510 yr For updating to the latest Plex, what about making the "version string" user definable? going to plex.tv one could easily find the current stable or plex-pass version and input it themselves. no need plex is auto updatable now following the script made by Kode
July 8, 201510 yr For updating to the latest Plex, what about making the "version string" user definable? going to plex.tv one could easily find the current stable or plex-pass version and input it themselves. in a docker environment the unraid package would be useless... that's a slack pack... dockers are linux distros like ubuntu or arch and so on.
Archived
This topic is now archived and is closed to further replies.