Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Roxedus

Community Developer
  • Joined

  • Last visited

Everything posted by Roxedus

  1. 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.
  2. the container doesnt need to be updated. restart the container, if that doesnt bring it up to date, check the container logs.
  3. 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.
  4. What makes it dead?
  5. 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/
  6. 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.
  7. https://github.com/Organizr/docker-organizr/commits/master/
  8. You do not *need* to do those changes.
  9. I see you already filed this, thanks https://github.com/causefx/Organizr/issues/1913
  10. You just need to restart the container, you can also use the update button in organizr.
  11. 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/
  12. Upstream_port is 80
  13. No, i have no idea on the projects roadmap
  14. This thread is related for support for the templates themself, app support is only a bonus.
  15. Considering unraid is the only plattform offering this, its not unreasonable to ask users to somewhat keep up with the updates for a container.
  16. Thanks. built a new image.
  17. Wil FCP or CA warn users if any or both of these is true?
  18. This has been the case for years
  19. Perfect, that's how I was hoping it behaved, will work that into our generator
  20. Will this potential feature support branch-specific values? as in a readme for main, develop etc when using the Branches tag
  21. 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
  22. 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.
  23. I updated it 16 hours ago.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.