Roxedus

You claim the initial reviewer did not look at the repo, because the comment, and action happened in the same minute. You do realize there is a window of more than an hour from when you opened the PR to the action was taken, right. That's a lot of time to review. I have never commented that I start reviewing anything, the review and action just arrives. In a issue reply you asked for a policy, which was present, it doesn't explicitly call out the PR content, but the nature of the policy clearly states that there is some requirements for AI, which did not make it into the PR at all (did your agent miss it?). I find the lack of acknowledgement for the present policy disrespectful, it probably also added to the decision that was made. We may act god-like, it's our repo, it's not the single way in to CA, It's not the decider for apps to be added to CA. It is not affiliated with Limetech nor the maintainer of the Community Applications plugin. This style of CA repo was (and maybe even still is) unprecedented, as there was no established repo that accepted "outsiders" (as in non-established persons in the ecosystem) to add applications, so additional screening needs to take place, as the blast-radius for getting the repo removed/banned affects quite a few different style of apps.

Im actually 7.

the container doesnt need to be updated. restart the container, if that doesnt bring it up to date, check the container logs.

I messed up the network entry, sorry about that. I am going to update the template, but you have to set that yourself on your current install.

What makes it dead?

Pushing a non-working latest tag is how we have been deprecating images for a year, we do this in order to let people know it is deprecated. https://info.linuxserver.io/issues/2024-08-11-deprecation-changes/

Do you really need to send a TZ different from the unraid server itself? TZ is automatically set by dockerman, for all containers it creates.

https://github.com/Organizr/docker-organizr/commits/master/

You do not *need* to do those changes.

I see you already filed this, thanks https://github.com/causefx/Organizr/issues/1913

You just need to restart the container, you can also use the update button in organizr.

I have been making sure it builds and runs, other than that I haven't spent much time on this. I do see there is a official container now, so that's probably the one you want to use. https://technitium.com/dns/

🙏

Upstream_port is 80

No, i have no idea on the projects roadmap