[Plug-In] Community Applications

[MyKroFt]

Have you even thought of allowing remote backup locations?  Maybe with this method = https://lime-technology.com/forum/index.php?topic=46663.msg445897#msg445897

 

Myk

[Squid]

Have you even thought of allowing remote backup locations?  Maybe with this method = https://lime-technology.com/forum/index.php?topic=46663.msg445897#msg445897

 

Myk

Has a dependency, which for something like CA I don't want.  (for something like CA with its pervasiveness, dependencies are avoided at all costs since it's probably used on 90+% of unRaid systems out there)

 

But, seems to me you could easily make a script that monitors for changes in the backup destination, then runs rclone and moves the stuff over to the remote location.

 

And then we're also back to a symlink issue and whether or not a rclone destination supports it.  And ultimately if the destination doesn't handle the symlinks, then its not going to be a proper backup (and as per a couple posts up, not all UD destinations support symlinks either)

 

[dalben]

Not sure if it's been mentioned but in the Backup Appdata plugin, I can't find a way to exclude subdirectories withing the root level subdirectories.

 

I want to exclude all cache types directories because come backup/restore time, restoring cache files are a luxury I don't need.  Is there any way to drill down to these types of subdirectories ?

[Squid]

Not sure if it's been mentioned but in the Backup Appdata plugin, I can't find a way to exclude subdirectories withing the root level subdirectories.

 

I want to exclude all cache types directories because come backup/restore time, restoring cache files are a luxury I don't need.  Is there any way to drill down to these types of subdirectories ?

The file tree that I'm using doesn't support that without a rewrite of its api (ie: if I dig into a subdirectory of it, it returns the name of the subdirectory instead of the path including the parent.)  What you're going to have to do is specify it in the rsync options instead.

 

Off the top of my head (at work so can't check), you would add something like this

--exclude sabnzbd/downloads

 

[dalben]

Not sure if it's been mentioned but in the Backup Appdata plugin, I can't find a way to exclude subdirectories withing the root level subdirectories.

 

I want to exclude all cache types directories because come backup/restore time, restoring cache files are a luxury I don't need.  Is there any way to drill down to these types of subdirectories ?

The file tree that I'm using doesn't support that without a rewrite of its api (ie: if I dig into a subdirectory of it, it returns the name of the subdirectory instead of the path including the parent.)  What you're going to have to do is specify it in the rsync options instead.

 

Off the top of my head (at work so can't check), you would add something like this

--exclude sabnzbd/downloads

 

I have an rsync script I cobbled together that uses and exclude file which excludes the subdirectories I want excluded.  I'll have a play and see if I can incorporate the reading of that exclude file.

 

Thanks

[Squid]

Not sure if it's been mentioned but in the Backup Appdata plugin, I can't find a way to exclude subdirectories withing the root level subdirectories.

 

I want to exclude all cache types directories because come backup/restore time, restoring cache files are a luxury I don't need.  Is there any way to drill down to these types of subdirectories ?

The file tree that I'm using doesn't support that without a rewrite of its api (ie: if I dig into a subdirectory of it, it returns the name of the subdirectory instead of the path including the parent.)  What you're going to have to do is specify it in the rsync options instead.

 

Off the top of my head (at work so can't check), you would add something like this

--exclude sabnzbd/downloads

 

I have an rsync script I cobbled together that uses and exclude file which excludes the subdirectories I want excluded.  I'll have a play and see if I can incorporate the reading of that exclude file.

 

Thanks

It just use that script instead of the built in one.  CA will stop and start the apps automatically and then run your script

 

Sent from my LG-D852 using Tapatalk

 

 

[dalben]

Not sure if it's been mentioned but in the Backup Appdata plugin, I can't find a way to exclude subdirectories withing the root level subdirectories.

 

I want to exclude all cache types directories because come backup/restore time, restoring cache files are a luxury I don't need.  Is there any way to drill down to these types of subdirectories ?

The file tree that I'm using doesn't support that without a rewrite of its api (ie: if I dig into a subdirectory of it, it returns the name of the subdirectory instead of the path including the parent.)  What you're going to have to do is specify it in the rsync options instead.

 

Off the top of my head (at work so can't check), you would add something like this

--exclude sabnzbd/downloads

 

I have an rsync script I cobbled together that uses and exclude file which excludes the subdirectories I want excluded.  I'll have a play and see if I can incorporate the reading of that exclude file.

 

Thanks

It just use that script instead of the built in one.  CA will stop and start the apps automatically and then run your script

 

Sent from my LG-D852 using Tapatalk

 

Cool, thanks.

[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

[Squid]

I'll check it out.  Any chance you can zip up the contents of boot/config/plugins/dockerMan/templates-user and pm it to me?

 

Sent from my LG-D852 using Tapatalk

 

 

[Squid]

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

Sure, find a bug for a use case that I never thought of.  In this case, you're running an app that doesn't have any volume mappings.

 

Fixed and updated.  I guess that you should now be listed as a tester, since CHBMB doesn't seem to be doing his job as of late   

[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

Sure, find a bug for a use case that I never thought of.  In this case, you're running an app that doesn't have any volume mappings.

 

Fixed and updated.  I guess that you should now be listed as a tester, since CHBMB doesn't seem to be doing his job as of late   

 

You are welcome.

[Marv]

 

EDIT: And to drive home the point again, ALL FILES WITHIN THE BACKUP DESTINATIONS CAN BE DELETED WHEN A BACKUP RUNS.  ONLY USE A SHARE / DESTINATION SPECIFICALLY FOR THE BACKUP.  IF YOU DELETE YOUR ENTIRE MEDIA COLLECTION BECAUSE OF A WRONG SETTING, ITS NOT MY PROBLEM  That being said, I did take some precautions.  You're not allowed to set a destination of /mnt/disk1 or /mnt/cache or /mnt/user, etc for the USB backup.  USB Backup (when on a separate destination) cannot be a sub folder of the appdata backup destination, etc

 

Hi,

 

just for me to understand.

Why am I not allowed to set a destination such as /mnt/user/Backup/USB for the USB backup (seperate destination)

and /mnt/disk2/Backup/appdata for the cache appdata folder?

Or do I misinterpret the quote above?

[Squid]

You misinterpreted.  Separate destinations are allowed

 

Sent from my LG-D852 using Tapatalk

 

 

[thegorgotron]

I'm pretty sure I've said this already, but this is fucking great!!!!!

[thejamkel]

Hey folks anyone having issues with App updates displaying as Not Available after trying to update and the following error message being displayed:

 

 

Download of appfeed failed. Reverting to legacy mode

 

Download of source file has failed

Last Change To Appfeed:

[Squid]

Hey folks anyone having issues with App updates displaying as Not Available after trying to update and the following error message being displayed:

 

 

Download of appfeed failed. Reverting to legacy mode

 

Download of source file has failed

Last Change To Appfeed:

Sounds like your dns settings and or gateway is messed up in network settings

 

Sent from my LG-D852 using Tapatalk

 

 

[thejamkel]

Thanks Squid, looks like my DNS server had vanished.. I should have checked that first! Thanks for the response.

[smdion]

is this "DISK_ASSIGNMENTS.txt" file on my flash drive your voodoo. If so, I bow to you.

[Squid]

is this "DISK_ASSIGNMENTS.txt" file on my flash drive your voodoo. If so, I bow to you.

 

Created (and updated) with every backup

[thomast_88]

Hi

 

I'm trying to pass in a variable which contains a ';' in the value (it's a convention when using the official GitLab docker and you want to change some configuration key/value pairs: http://docs.gitlab.com/omnibus/docker/)

 

However i encounter an issue as soon as i click "Add Container" or try to update the container with this particular variable.

 

Variable name: GITLAB_OMNIBUS_CONFIG
Variable value: external_url 'http://my.domain.com/'; gitlab_rails['lfs_enabled'] = true;

 

I also tried adding it directly into the "Extra Parameters" like this:

 

--env GITLAB_OMNIBUS_CONFIG="external_url 'http://my.domain.com/'; gitlab_rails['lfs_enabled'] = true;" 

 

but i still get the same error:

 

The command failed.
sh: /usr/local/emhttp: Is a directory

 

Attached some screenshots as well

 

[saarg]

Hi

 

I'm trying to pass in a variable which contains a ';' in the value (it's a convention when using the official GitLab docker and you want to change some configuration key/value pairs: http://docs.gitlab.com/omnibus/docker/)

 

However i encounter an issue as soon as i click "Add Container" or try to update the container with this particular variable.

 

Variable name: GITLAB_OMNIBUS_CONFIG
Variable value: external_url 'http://my.domain.com/'; gitlab_rails['lfs_enabled'] = true;

 

I also tried adding it directly into the "Extra Parameters" like this:

 

--env GITLAB_OMNIBUS_CONFIG="external_url 'http://my.domain.com/'; gitlab_rails['lfs_enabled'] = true;" 

 

but i still get the same error:

 

The command failed.
sh: /usr/local/emhttp: Is a directory

 

Attached some screenshots as well

 

Does the same thing happen if you run the command in command line?

Just go edit the container, remove the problem variable and hit save. Then you will have the docker run command in the last command box. Copy it and ssh into your server and issue the command with the added problem variable. If that works, use the full path from /usr/local/emhttp/etc... and see if that works. If not, it's a bug in dockerman.

[CHBMB]

Does the same thing happen if you run the command in command line?

Just go edit the container, remove the problem variable and hit save. Then you will have the docker run command in the last command box. Copy it and ssh into your server and issue the command with the added problem variable. If that works, use the full path from /usr/local/emhttp/etc... and see if that works. If not, it's a bug in dockerman.

 

Good idea.  I dunno much about these things but is it something about the semicolon and the php of CA?  That would only be the case if it worked ok via command line though.

[Squid]

Does the same thing happen if you run the command in command line?

Just go edit the container, remove the problem variable and hit save. Then you will have the docker run command in the last command box. Copy it and ssh into your server and issue the command with the added problem variable. If that works, use the full path from /usr/local/emhttp/etc... and see if that works. If not, it's a bug in dockerman.

 

Good idea.  I dunno much about these things but is it something about the semicolon and the php of CA?  That would only be the case if it worked ok via command line though.

It's not going to be CA.

 

Sent from my LG-D852 using Tapatalk

 

 

[thomast_88]

Hi

 

I'm trying to pass in a variable which contains a ';' in the value (it's a convention when using the official GitLab docker and you want to change some configuration key/value pairs: http://docs.gitlab.com/omnibus/docker/)

 

However i encounter an issue as soon as i click "Add Container" or try to update the container with this particular variable.

 

Variable name: GITLAB_OMNIBUS_CONFIG
Variable value: external_url 'http://my.domain.com/'; gitlab_rails['lfs_enabled'] = true;

 

I also tried adding it directly into the "Extra Parameters" like this:

 

--env GITLAB_OMNIBUS_CONFIG="external_url 'http://my.domain.com/'; gitlab_rails['lfs_enabled'] = true;" 

 

but i still get the same error:

 

The command failed.
sh: /usr/local/emhttp: Is a directory

 

Attached some screenshots as well

 

Does the same thing happen if you run the command in command line?

Just go edit the container, remove the problem variable and hit save. Then you will have the docker run command in the last command box. Copy it and ssh into your server and issue the command with the added problem variable. If that works, use the full path from /usr/local/emhttp/etc... and see if that works. If not, it's a bug in dockerman.

 

Ok i tried both things, this is the result:

 

docker run (works fine):

root@unRAID:/mnt/user/appdata# docker run -d --name="GitLab-CE" --net="bridge" -e TZ="Europe/Paris" -e HOST_OS="unRAID" -p 45300:80/tcp -p 45305:443/tcp -p 45310:22/tcp -v "/mnt/cache/appdata/gitlab-ce/config":"/etc/gitlab":rw -v "/mnt/cache/appdata/gitlab-ce/data":"/var/opt/gitlab":rw -v "/mnt/cache/appdata/gitlab-ce/log":"/var/log/gitlab":rw --env GITLAB_OMNIBUS_CONFIG="external_url 'http://my.domain.com/'; gitlab_rails['lfs_enabled'] = true;" gitlab/gitlab-ce
724e403bc962631a9aa773d24f8657055f6d18f6db854a38794916e4bcf7680e

 

docker run full path (works fine):

root@unRAID:/mnt/user/appdata# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name="GitLab-CE" --net="bridge" -e TZ="Europe/Paris" -e HOST_OS="unRAID" -p 45300:80/tcp -p 45305:443/tcp -p 45310:22/tcp -v "/mnt/cache/appdata/gitlab-ce/config":"/etc/gitlab":rw -v "/mnt/cache/appdata/gitlab-ce/data":"/var/opt/gitlab":rw -v "/mnt/cache/appdata/gitlab-ce/log":"/var/log/gitlab":rw --env GITLAB_OMNIBUS_CONFIG="external_url 'http://my.domain.com/'; gitlab_rails['lfs_enabled'] = true;" gitlab/gitlab-ce
7b3c680e8609383b4d28d9f134d4735c162acfd6a1811e5ca0dcbe5ba8c9604b

 

So it must be something in the WebUI i suppose?

[saarg]

Hi

 

I'm trying to pass in a variable which contains a ';' in the value (it's a convention when using the official GitLab docker and you want to change some configuration key/value pairs: http://docs.gitlab.com/omnibus/docker/)

 

However i encounter an issue as soon as i click "Add Container" or try to update the container with this particular variable.

 

Variable name: GITLAB_OMNIBUS_CONFIG
Variable value: external_url 'http://my.domain.com/'; gitlab_rails['lfs_enabled'] = true;

 

I also tried adding it directly into the "Extra Parameters" like this:

 

--env GITLAB_OMNIBUS_CONFIG="external_url 'http://my.domain.com/'; gitlab_rails['lfs_enabled'] = true;" 

 

but i still get the same error:

 

The command failed.
sh: /usr/local/emhttp: Is a directory

 

Attached some screenshots as well

 

Does the same thing happen if you run the command in command line?

Just go edit the container, remove the problem variable and hit save. Then you will have the docker run command in the last command box. Copy it and ssh into your server and issue the command with the added problem variable. If that works, use the full path from /usr/local/emhttp/etc... and see if that works. If not, it's a bug in dockerman.

 

Ok i tried both things, this is the result:

 

docker run (works fine):

root@unRAID:/mnt/user/appdata# docker run -d --name="GitLab-CE" --net="bridge" -e TZ="Europe/Paris" -e HOST_OS="unRAID" -p 45300:80/tcp -p 45305:443/tcp -p 45310:22/tcp -v "/mnt/cache/appdata/gitlab-ce/config":"/etc/gitlab":rw -v "/mnt/cache/appdata/gitlab-ce/data":"/var/opt/gitlab":rw -v "/mnt/cache/appdata/gitlab-ce/log":"/var/log/gitlab":rw --env GITLAB_OMNIBUS_CONFIG="external_url 'http://my.domain.com/'; gitlab_rails['lfs_enabled'] = true;" gitlab/gitlab-ce
724e403bc962631a9aa773d24f8657055f6d18f6db854a38794916e4bcf7680e

 

docker run full path (works fine):

root@unRAID:/mnt/user/appdata# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name="GitLab-CE" --net="bridge" -e TZ="Europe/Paris" -e HOST_OS="unRAID" -p 45300:80/tcp -p 45305:443/tcp -p 45310:22/tcp -v "/mnt/cache/appdata/gitlab-ce/config":"/etc/gitlab":rw -v "/mnt/cache/appdata/gitlab-ce/data":"/var/opt/gitlab":rw -v "/mnt/cache/appdata/gitlab-ce/log":"/var/log/gitlab":rw --env GITLAB_OMNIBUS_CONFIG="external_url 'http://my.domain.com/'; gitlab_rails['lfs_enabled'] = true;" gitlab/gitlab-ce
7b3c680e8609383b4d28d9f134d4735c162acfd6a1811e5ca0dcbe5ba8c9604b

 

So it must be something in the WebUI i suppose?

Looks like a webgui bug then. You should file a defect report so it gets picked up.