Selfhosted
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:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
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!
view the rest of the comments
Is there a buried lede here? What’s noteworthy about an RC of a minor version release?
This is the database rework that's been in progress for a while to remove all the bad inherited database code from when the forked Emby. No more SQL statements in code or plugins, any DB access now goes through the core library. There are a few blog posts in their website with more details.
I'll be honest, Im not sure why theyre not releasing this as 11.x.
This seems to be a major update. From what I can tell there are API changes, plugins might not work, your entire db is converted to another format, etc.
I'm excited for it and thankful for all the work- just seems so big that it should be tagged 11.0.0
I kinda agree here. https://jellyfin.org/docs/general/contributing/release-procedure/
Claims to follow semantic versioning, explicitly mentioning changes to plugin APIs as reasoning for a new major version.
Their reasoning is literally the second sentence on that page.
Any 10.Y.Z release is cleanup and can include breaking changes. That's been the case for 10.9 and 10.10 already btw.
Sure they put a note in, but why not just follow semver to begin with instead of using semver with a bunch of asterisks, and essentially ignoring what semver is?
Out of curiosity, this is better because of encapsulation? Protection from bad plugins?
Basically, yes. Forces plugins not to use potentially database-engine-specific SQL so that server admins don't have to select their DB based on plugins for jellyfin being compatible.
Brilliant. 👍
I'm serious, there's so much lazy posting on Lemmy regarding software releases.
Jellyfin is quite a big name, but still, the pattern is clear.
I have to admit, it's something I'd like to see done a bit better (not that I'd be the one posting about it typically)
"Crocoslut version 12 released!"
Uh... great?
Though sometimes you go to the website and it's not much better.
Dude yes. Among my comments you'll see that I ranted about this for a few days in the comments of another post. That's even worse, when you can't even find out for yourself.
Crocoslut really started going downhill after the license change and conversion to nodejs in v9.
Crocoslut is yesterday. AlligatorAlly is the more friendly fork!
We could have a tag for things like this (if tags are a thing on lemmy) or a required prefix, such as "Software release: ".
I do like to see an announcement for things I use and have slow release schedule.
Sorry, I didn’t realize some Lemmy clients don’t show cross-post descriptions. I’ll copy paste it below:
WIP release notes: https://notes.jellyfin.org/v10.11.0_features
This is the first release that uses the new EF Core database mapper. If you'd like to help test this release, please remember to remove all plugins to make debugging logs as easy as possible.
My client showed that to me and I read it. I just imagined myself as someone who doesn't know what Jellyfin is, and that text didn't help much.