smdion

Hey Squid.. got this on the appdata cleanup Warning: Invalid argument supplied for foreach() in /usr/local/emhttp/plugins/community.applications/include/exec.php on line 2165 Warning: Invalid argument supplied for foreach() in /usr/local/emhttp/plugins/community.applications/include/exec.php on line 2165 No orphaned appdata folders found

Thanks for this Squid.

I bow to your greatness CHBMB

I also see this on Beta 23 still.

Nobody searches in this thread as 90+% of the posts are all OT (just the way I like it ) But my stance on flash drive backup hasn't changed. And TBH I don't really see much need for it as in this world of VMs and Docker, most of the settings are actually stored within the array / docker image / system image etc. Only thing is the user template XMLs for docker and XMLs for VMs (passthru) stored on flash drive. I know I'm probably an odd use-case here, but when I had my flash drive die resetting up all my volume/port mappings was a real PITA. That would be the only argument I have for the flash drive. EDIT: I agree its most of the time a one time backup, but adding some ease for users would be nice. Good point. But its such an easy thing to do yourself that it's almost criminal to not do it yourself periodically. /whinyvoice but I want someone else to set it up for me to happen automatically Already exists: Read here and And here

Nobody searches in this thread as 90+% of the posts are all OT (just the way I like it ) But my stance on flash drive backup hasn't changed. And TBH I don't really see much need for it as in this world of VMs and Docker, most of the settings are actually stored within the array / docker image / system image etc. Only thing is the user template XMLs for docker and XMLs for VMs (passthru) stored on flash drive. I know I'm probably an odd use-case here, but when I had my flash drive die resetting up all my volume/port mappings was a real PITA. That would be the only argument I have for the flash drive. EDIT: I agree its most of the time a one time backup, but adding some ease for users would be nice. Good point. But its such an easy thing to do yourself that it's almost criminal to not do it yourself periodically. /whinyvoice but I want someone else to set it up for me to happen automatically I agree with you though.

Nobody searches in this thread as 90+% of the posts are all OT (just the way I like it ) But my stance on flash drive backup hasn't changed. And TBH I don't really see much need for it as in this world of VMs and Docker, most of the settings are actually stored within the array / docker image / system image etc. Only thing is the user template XMLs for docker and XMLs for VMs (passthru) stored on flash drive. I know I'm probably an odd use-case here, but when I had my flash drive die resetting up all my volume/port mappings was a real PITA. That would be the only argument I have for the flash drive. EDIT: I agree its most of the time a one time backup, but adding some ease for users would be nice.

No. It's just forcing unRaid to use a particular address to resolve domain names (in this case Google's DNS servers) and bypassing whatever your ISP has chosen to use (in my case, Bell Sympatico's DNS servers are beyond crap) Hey Squid... Love the appdata backup part of this, any chance of adding a /boot backup as well? See here /hangs head in shame that he didn't search. Thanks Trurl

No. It's just forcing unRaid to use a particular address to resolve domain names (in this case Google's DNS servers) and bypassing whatever your ISP has chosen to use (in my case, Bell Sympatico's DNS servers are beyond crap) Hey Squid... Love the appdata backup part of this, any chance of adding a /boot backup as well?

Quick Google-foo seems like it does https://www.reddit.com/r/sonarr/comments/4ggkaj/what_exactly_is_the_point_of_use_hardlinks/d2hpvdv I don't have much first hand experience with it though...

Seconded. Same problem. I'm updating my PlexPy now.. I'll see if it breaks mine and let you know what I do to fix it. EDIT: Seems okay for me Apache Config: <Location /plexpy> ProxyPass http://10.10.10.12:8181/plexpy/ ProxyPassReverse http://10.10.10.12:8181/plexpy/ </Location> PlexPy config.ini http_root = /plexpy http_proxy = 0

Hey bb12489, I wrote a guide a while back for Apache (https://www.linuxserver.io/index.php/overview-reverse-proxy-with-docker/). I just converted over to nginx and do not have a write up yet (i plan too, just been busy) Here is my old apache config - https://www.seandion.com/owncloud/index.php/s/R4tJqfqb4opuOsp Here is my new nginx config - https://www.seandion.com/owncloud/index.php/s/XpFigScMblZO2dJ Those should help a bit more and I will be doing an nginx addition to that guide.

You could try a different view mode. Icon Details vs Icon vs Table

Yep, there is something gone on with the mirror that you are trying to pull from. People get different mirrors assigned to them based on their physical location. Even though you are installing from the same place (https://hub.docker.com/r/linuxserver/sabnzbd/), the mirrors attempt to get a server that is closest to you. The one that was assigned to you is having issues, if you try again in a few hours you should get a new mirror OR that mirror will have resolved its issues.

Nice work as always Squid

You need to leave "Container port" as it is, but host port you can change however you want!

You can change piwigo to run on any port by changing the "host port" in the docker web page on the unRAID WebGUI.

I do see he has an ubuntu guide (https://github.com/wnielson/Plex-Remote-Transcoder/wiki/Ubuntu-Install) you could always docker exec -it plex /bin/bash into your terminal window when your SSH'd into unRAID and add those features yourself?

False is the default setting on settings.json I agree was from your previous docker. https://github.com/linuxserver/docker-transmission/blob/master/defaults/settings.json

Waiting on an audit and the linuxserver.io version will be out

The supported way is --bridge and you can change the HOST port in the WebGUI, sorry

If you do a search for plexpy in Community Apps, this does show up

I may have jumped the gun nginx is 99.9% ready. Very soon It is also still in my repo until that point.

I have (finally) transitioned all* of my dockers to LinuxServer.io's repo. There will be no additional updates to my smdion repo and current dockers will continue to work as-is(meaning no support). As noted before I've joined the great group at http://www.linuxserver.io and am creating dockers with the team over there. This will ensure when/if I disappear for a long period of time again that the dockers are supported. Due to the great features of the LinuxServer.io dockers (Auto Updates on Startup, Run as any user, Standard folder configurations, great documentation, multiple people creating/supporting dockers), there is no "standard" migration path from my dockers, which did not have these features. You should be able to move over most of the config files and change around some paths to get them working. All LinuxServer.io's dockers are available in the Community apps. I have deleted all of smdion's repo dockers out of Community Apps to stop any confusion. Please post any questions/comments/concerns here. *UpStatsboard, H5AI were not transferred due to no updates from project author (upstatsboard) and lack of interest (h5ai)