[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