dockerPolice

If changes to the template are required, you should talk to LinuxServer on their discord about making those changes.

https://pydio.com/en/features/why-migrating-pydio-8-cells

Am I correct in assuming then that linuxserver/pydio is now deprecated (since it is Pydio-8 which Pydio is recommending to migrate to pydio-cells)?

They're all from prior to his joining lsio, and since DigiKam had no direct replacement in another active repository, it stayed within Apps. Now it's officially deprecated, (along with JDownloader2 - as there's other replacements for that one also)

Along with the repository that it's pulling from. Not to mention that the original displays Seems to me that the template should be updated

Certainly appears to be as of a week ago. (https://blog.linuxserver.io/2020/08/21/introducing-swag/) I would expect that @aptalca will shortly adjust the Unraid template to reflect this change.

Removed due to zero support, no updates in 3 years+, fundamentally very limited drivers included that would work on an ancient printer that isn't commonly available nowadays and far far better alternatives to what was available within CA by enabling Docker Hub Searches within CA and then searching for CUPS. IE: Not much point in keeping an app within CA that for the most part doesn't work as advertised. https://forums.unraid.net/topic/37549-support-gfjardims-docker-repository/page/14/?tab=comments#comment-827842 Review the last page or 2 of the linked content to see some of the examples of alternatives that actually work.

And, unlike the other F@H app, it won't automatically join Team unRaid (quite understandable). The team # if you care is 227802

I think that I'm going to remove CUPS from CA. It's one of those abandoned applications. While it does somewhat work, it's not particularly populated with printer drivers that are more commonly used today, and there are many more choices for CUPS available @ dockerHub that are kept more up to date and have a better selection of drivers within them.

Because based upon support requests here in the forum and activity of the OP of the thread, you can reasonably expect no support via the official channels here in this forum regarding any unRaid specific issues. The support on the whole for emby via their own forum / discord / whatnot may be amazing, but my recommendations are based upon support you can get here. And it's purely a personal opinion...

At the heart of it, there is no fundamental difference. ie: Emby is emby is emby. Difference lies in some subtleties. and as @jonathanm stated support regarding hardware transcoding. lsio issues updates for the containers if the base OS has an update (security patch), or emby get's updated pretty much the minute that it happens. binhex issues updates for the containers whenever the arch upstream repository for emby gets updated (which will lag behind the actual updates) emby issues updates for the containers whenever they release a new stable version (ie: 2 months ago) or if you installed the beta version 2 days ago. No clue about their security policies. If you're going to be using the nVidia plugin, you're definitely going to want to run the lsio version, as it'll at least be tested with the nvidia hardware transcoding. Everything else probably only supports intel GPU transcoding if you passthrough the appropriate commands and have a compatible (ie: older iGPU) All else being equal and if you're not doing hardware transcoding, you're looking at either lsio or @binhex ie: Long story short, you're not the first to ask this type of question (although usually it's about Plex), CA has this policy

I was actually concerned that br0 wasn't available by default, but since it is this isn't really that big a deal

Does this have to run on it's own IP??? Would it be better to have the default for the template set to be bridge with the appropriate ports mapped through?

Nothing says you can't run ps3netsrv. Only that mccloud/ps3netsrv now will install cryptomining software. AFAIK there are other ps3netsrv's available on dockerHub that will work fine for you (enable dockerHub searches within the apps tab)

mccloud/ps3netsrv and mccloud/ps3netsrv:latest will have a warning go out via FCP regarding its infection with crypto mining software. However, it should be noted that this apparent breach of mccloud's GitHub repo happened in and around 10 hours ago today. PS3Netsrv has NOT been available within Community Applications for a while now, as the tags utilized by the templates within CA were no longer available to be downloaded. At that point, all of the users of the previous tags for ps3netsrv (:alpine, :debian, etc) were also notified via Fix Common Problems that the containers were blacklisted because of the tags no longer being available. At no point has the :latest tag with regards to ps3netsrv from McCloud ever been available within CA as the template maintainer never updated the templates to reflect the new tags. (The :latest tag is the one with the crypto mining software) While this breach doesn't affect any applications that are available within Community Applications (Apps), the moderators of CA take very seriously the security and integrity of the applications present within.