Roxedus

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

This thread is related for support for the templates themself, app support is only a bonus.

Considering unraid is the only plattform offering this, its not unreasonable to ask users to somewhat keep up with the updates for a container.

Thanks. built a new image.

Wil FCP or CA warn users if any or both of these is true?

This has been the case for years

Perfect, that's how I was hoping it behaved, will work that into our generator

Will this potential feature support branch-specific values? as in a readme for main, develop etc when using the Branches tag

Is there a way to fully emulate, and test how a template would be shown if it was a "true" CA template? mostly wanting to test Branches, and the extra links showing in the CA card

This "fix", is needed because the container gets forcefully shut down, before mariadb has successfully shutdown, this is usually isn't a problem, as mariadb is nice, and usually manages to recover from a dirty shutdown. The docker update plugin uses 10s as the default time before killing a container, which does not suffice.

I updated it 16 hours ago.

I love breaking stuff.

Because the config you posted expose it on organizr.domain.com, not domain.com. That's why I asked, and waited for a answer To clarify, domain.com in this context is supposed to be substituted with your real domain