Selfhosted

62003 readers

1185 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Detailed Rules Post

Be civil.
No spam.
Posts are to be related to self-hosting.
Don't duplicate the full text of your blog or readme if you're providing a link.
Submission headline should match the article title.
No trolling.
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

561

Jellyfin 12 Released (github.com)

submitted 1 day ago by Mountaineer@aussie.zone to c/selfhosted@lemmy.world

121 comments fedilink hide all child comments

cross-posted from: https://aussie.zone/post/36389875

Why jump from 10.11.11 directly to 12.0? -> Blog Post

You can find more details about and discuss this release on the official forums.

As always, please ensure you stop your Jellyfin server and take a full backup of your metadata/configs before upgrading!

Direct upgrades from 10.10.7 and 10.11.x to 12.0 are supported; intermediate upgrades are not required. Users running releases older than 10.10.7 are strongly encouraged to upgrade to 10.10.7 before migrating to 12.0.

Installed repository plugins (anything not built-in) should also be removed before migrating. Plugins will likely need time to adapt to the new database changes, so re-adding them afterward is the safest approach for testing.

Official plugins compatible with Jellyfin are available through the stable plugin repository. If you have changed to the unstable plugin repository please change it back.
Go to Dashboard -> Plugins -> Manage Repositories
Update the Plugin Repository URL to: https://repo.jellyfin.org/files/plugin/manifest.json
After migrating please perform the following steps.
Perform a full library scan to restore alternative versions
Run the "Optimize database" scheduled task
___

you are viewing a single comment's thread
view the rest of the comments

[–] EncryptKeeper@lemmy.world 18 points 17 hours ago (2 children)

My wait for OIDC support for sensible client logins continues

[–] irish_link@lemmy.world 3 points 8 hours ago (1 children)

I know it’s not the same but quick connect works well. Why not log in that way using a six digit code?

[–] EncryptKeeper@lemmy.world 1 points 5 hours ago (1 children)

Couple reasons.

Jellyfin is not security software, and given the inconsistency and general lack of polish of every other aspect of Jellyfin, its raw login page is not something I’d comfortably expose to the internet to begin with.
Quick connect is a poor, unintuitive imitation of Device Flow. A non-technical user would have to also have a Jellyfin app or bookmark in their phone already, and know where to navigate in it to reach the quick connect function. This on its own is insurmountable.
It’s not SSO. Jellyfin is yet another username and password they must remember when every single other thing I self host supports OIDC out of the box and they get one user account for everything.

[–] irish_link@lemmy.world 1 points 3 hours ago

Fair points. Thanks for the lesson. TIL a lot.

Man, I really appreciate so many good folks giving info and not flaming each other. This is a great community.

[–] quadrant5835@lemmy.zip 2 points 12 hours ago (1 children)

I agree with you but also about 90% of watching on my instance happens on smart TV's. So even though I would like to have oidc supported for the occasional phone/pc user I would still need something basic that a TV can use.

[–] EncryptKeeper@lemmy.world 4 points 12 hours ago* (last edited 12 hours ago)

Smart TVs should be able to support OIDC easily out of the box.

And if it didn’t, you can just use a Device Flow