[email protected]

Updated, thanks for the heads up.

Thanks for the heads up, updated

Little friendly advice man, when you think someone is mistaken, it's a lot nicer to kindly point them in the right direction rather than putting them on blast in a blog post. My automated monitoring system relies on the app developers updating certain files, typically Docker Compose files, which hasn't been updated for TinyAuth. I was not monitoring their documentation files. Looking at the changes now.

I don't see any documented changes in terms of Docker container setup for v5. Issues with the config or anything inside the container are best directed at the upstream developer: https://github.com/steveiliop56/tinyauth/issues?q=sort%3Aupdated-desc%20is%3Aissue%20is%3Aopen

There's a copy-paste error with the template that I just patched. Expand the advanced settings and edit Data Path to replace "dynamix" with "sync_in".

If you edit the template (you can change something and then immediately change it back) and click "Save", it should show a docker run command. Please post that here with secrets censored.

Sounda like an issue with the Docker startup and not the config file. Does the app even start, or does it quite immediately? What does your template look like?

It looks like you have the file path /mnt/user/appdata/sync_in/environment.yaml/environment.yaml, because a quirk of Unraid's Docker is auto-generating paths, even though this is meant to be a file. Delete the environment.yaml FOLDER and add an environment.yaml FILE under sync_in

@bmartino1 Just now seeing this, will look into it.

You would add labels to your other Docker containers (via "Add another Path, Port, Variable, Label or Device" on the edit page) with details about what type, name, etc. of Uptime Kuma monitor you want running for that container. AutoKuma then reads those labels and auto-generates Uptime Kuma monitors accordingly. https://github.com/BigBoot/AutoKuma#usage-

That's a usage-specific thing that really should be included in the project's documentation or wiki. The template has a link to the project's GitHub page for support. Butterfingers, thanks for letting me know, pushing out an update.

I would get it if you had some variety in your app choice, but the fact that you joined CA only a week ago and immediately published a half-dozen apps that are all related to "making passive income" feels really scammy to me. These aren't even apps that necessarily make sense for an Unraid machine. They don't take advantage of NAS functionality, of mass storage, of a powerful GPU or CPU, nothing that the majority of people are running Unraid for.

Thanks for letting me know, pushing out an update now.

This is outdated. Tunarr as of August 2024 has a :latest tag and is currently not blacklisted on the app store. It was previously due to a configuration issue. The latest tag is also regularly updated now that Tunarr is out of beta. You can simply ignore this warning from Fix Common Problems.

Thanks for the heads up. Have a PR open to update the app details

Hopefully they overwrite their latest tag on Docker Hub and un-publish 1.3.0. In the meantime, you can edit the repository to pin to a specific version: https://hub.docker.com/r/fyb3roptik/threadfin/tags Ex. fyb3roptik/threadfin:1.2.35

It looks like that other contributor published their template shortly after I published mine, but since they both use the same Docker image, the Community Apps store says both are installed on your system. The spirit of the CA Store is to not have duplicates of the same exact Docker image. Since Seraphys is one of the devs of Profilarr, I'll reach out to them about deprecating my version and handing over official control to them. Thanks for letting me know.

Looks like the developer consolidated the frontend and backend into one container, I'll deprecate the two separate containers and add a new template for the new one, thanks for letting me know.

Hey there, thanks! The template is available here: https://github.com/nwithan8/unraid_templates/blob/main/templates/otterwiki.xml Feel free to open a PR if there's any changes. I also have a semi-automated process of monitoring upstream apps for changes; if you have a Docker Compose file in your repo, I can enroll it into the system, which will help me be notified if changes are made to the Docker app. 1. 99:100 is the standard user:group for Unraid, which helps avoid permission errors. It can be overridden by PUID and PGID (1000:1000 is also common in a lot of Docker containers). 2. I'll update the template to indicate that latest could cause breaking changes on major version releases, and offer the "2" tag as a stable branch. The issue will be I'll need to manually update the template with the new stable tag if a major version is ever released. And users using "2" won't necessarily be made aware that there's a new major version available. Ah, the joys of Docker version pinning :)

Nothing to do on my end, please direct to the GPU Stats GitHub linked earlier. Thread here: https://forums.unraid.net/topic/89453-plugin-gpu-statistics/

GitHubUpdated container 0.27 won't start on Unraid · Issue #129...Hi, I updated the container, added the new volumes and variables but now it won't start anymore - this is the output of the log: 14:14:11 web.1 | from /var/app/vendor/bundle/ruby/3.4.0/gems/activer...

I am working with the Dawarich developer on a PR to get it back in the CA store.

If you wouldn't mind, could you run the following command in your terminal while automatic1111 is using your GPU? This should give us information about the exact process name that automatic1111 is calling. ``` nvidia-smi && (nvidia-smi |tr -s ' '|grep -Eo "| [0123456789]+ N/A N/A [0-9]{3,} .*"|awk -F' ' '{system("s=$(cat /proc/"$4"/cmdline| tr \"\\0\" \" \");u=$(ps -o uname= -p "$4");echo "$1"sep"$4"sep$u sep"$7"sep$s" ) }'|sed 's/sep/\t/g') ```

I would suspect the underlying process running in automatic1111 is the same as what runs in Immich, meaning the plugin is falsely detecting the wrong app. GitHubgpustat-unraid/src/gpustat/usr/local/emhttp/plugins/gpust...An UnRAID plugin for displaying GPU status. Contribute to SimonFair/gpustat-unraid development by creating an account on GitHub. This would be something to ping @SimonF about.

I don't personally use Libation. Any questions about the application itself would be best directed to the upstream maintainer: https://github.com/rmcrackan/Libation