kiol
@kiol@lemmy.world
- Submitted 3 days ago to selfhosted@lemmy.world | 0 comments
- Comment on Jellyswarrm - reverse proxy all your Jellyfin servers from a single interface, presenting as a standard Jellyfin server, clients should work out of the box. 3 days ago:
Made a short podcast episode to highlight Jellyswarrm. Hope you enjoy podcast.james.network/…/happy-birthday-linux
- Comment on Jellyswarrm - reverse proxy all your Jellyfin servers from a single interface, presenting as a standard Jellyfin server, clients should work out of the box. 4 days ago:
Presuming jellyfin would actually be on the public internet?
- Comment on Jellyswarrm - reverse proxy all your Jellyfin servers from a single interface, presenting as a standard Jellyfin server, clients should work out of the box. 5 days ago:
Good question. Asked the developer here, so feel free to chime in: github.com/Angablade/…/1#issuecomment-3217864250
- Comment on Jellyswarrm - reverse proxy all your Jellyfin servers from a single interface, presenting as a standard Jellyfin server, clients should work out of the box. 5 days ago:
Haha, you certainly don’t have to host it at a public url over http.
- Comment on Jellyswarrm - reverse proxy all your Jellyfin servers from a single interface, presenting as a standard Jellyfin server, clients should work out of the box. 5 days ago:
What sort of conflicts?
- Comment on Jellyswarrm - reverse proxy all your Jellyfin servers from a single interface, presenting as a standard Jellyfin server, clients should work out of the box. 6 days ago:
Jellyfin plays the media. It doesn’t make it or upload it for you.
- Comment on Jellyswarrm - reverse proxy all your Jellyfin servers from a single interface, presenting as a standard Jellyfin server, clients should work out of the box. 6 days ago:
Keep in mind this isn’t federation. It is a way to access multiple independent servers via reverse proxy.
- Comment on Jellyswarrm - reverse proxy all your Jellyfin servers from a single interface, presenting as a standard Jellyfin server, clients should work out of the box. 6 days ago:
Here are some questions from Jellyfin-offtopic:
- I wouldn’t trust it especially with the new DB coming out. No way Jellyfin’s own DB supports multiple servers. It would be up to the tool to keep track of everything. And I’m assuming only one person is supposed to run that thing on multiple servers.
- How would this work when multiple people want to connect to others at the same time?
- Comment on Jellyswarrm - reverse proxy all your Jellyfin servers from a single interface, presenting as a standard Jellyfin server, clients should work out of the box. 6 days ago:
- Comment on How do you manage accessing multiple Plex and Jellyfin servers simultaneously? 6 days ago:
Yep, it has already been posted here. Cheers!
- Comment on Jellyswarrm - reverse proxy all your Jellyfin servers from a single interface, presenting as a standard Jellyfin server, clients should work out of the box. 6 days ago:
Yep, this was mentioned in that thread and it is so impressive it deserves a dedicated topic to promote itself. Seems it has only existed for a few hours!
- Comment on How do you manage accessing multiple Plex and Jellyfin servers simultaneously? 6 days ago:
Post inception. That post was linked from this thread, hahaha.
- Jellyswarrm - reverse proxy all your Jellyfin servers from a single interface, presenting as a standard Jellyfin server, clients should work out of the box.lemmy.world ↗Submitted 6 days ago to selfhosted@lemmy.world | 44 comments
- Comment on How do you manage accessing multiple Plex and Jellyfin servers simultaneously? 6 days ago:
Oh wow, repo is github.com/LLukas22/Jellyswarrm Jellyswarrm is a reverse proxy that lets you combine multiple Jellyfin servers into one place. If you’ve got libraries spread across different locations or just want everything together, Jellyswarrm makes it easy to access all your media from a single interface.
Working
- Unified Library Access – Browse media from multiple Jellyfin servers in one place.
- Direct Playback – Play content straight from the original server without extra overhead.
- User Mapping – Link accounts across servers for a consistent user experience.
- API Compatibility – Appears as a normal Jellyfin server, so existing apps and tools still work.
⚠️ In Progress
- Websocket Support – Needed for real-time features like SyncPlay (not fully reliable yet).
- Audio Streaming – May not function correctly (still untested in many cases).
- Automatic Bitrate Adjustment – Stream quality based on network conditions isn’t supported yet.
🚫 Not Planned
- Admin Functions – Server administration (user management, settings, etc.) won’t be supported through Jellyswarrm.----
- Comment on Here is the mockup pic for adding Oauth Scopes in Nextcloud, but how should it actually be implemented? 6 days ago:
Thanks, this helped me better understand what is going on. Tried to formulate a response: github.com/nextcloud/server/issues/26233#issuecom…
- Comment on How do you manage accessing multiple Plex and Jellyfin servers simultaneously? 6 days ago:
Thank you for checking!
- Submitted 6 days ago to selfhosted@lemmy.world | 8 comments
- Here is the mockup pic for adding Oauth Scopes in Nextcloud, but how should it actually be implemented?lemmy.world ↗Submitted 1 week ago to selfhosted@lemmy.world | 7 comments
- Comment on Garage - S3-compatible Object Storage alternative to Minio 2 months ago:
Sounds like a question to ask the project directly, via their contact on the site: garagehq@deuxfleurs.fr
- Comment on Garage - S3-compatible Object Storage alternative to Minio 2 months ago:
One sentence answer: “Object storage manages data as discrete units called objects with unique identifiers and metadata, while file storage organizes data in a hierarchical structure of files and folders.”
fwiw, I see object storage used as a way to manage data regardless of the file system. It is designed to scale, as opposed to the file system, in large cloud environments.
Here is a recap from Google Cloud:
Object storage, also known as object-based storage, is a computer data storage architecture designed to handle large amounts of unstructured data. Unlike other architectures, it designates data as distinct units, bundled with metadata and a unique identifier that can be used to locate and access each data unit.
These units—or objects—can be stored on-premises, but are typically stored in the cloud, making them easily accessible from anywhere. Due to object storage’s scale-out capabilities, there are few limits to its scalability, and it’s less costly to store large data volumes than other options, such as block storage.
Much of today’s data is unstructured: email, media and audio files, web pages, sensor data, and other types of digital content that do not fit easily into traditional databases. As a result, finding efficient and affordable ways to store and manage it has become problematic. Increasingly, object storage has become the preferred method for storing static content, data arches, and backups.
- Comment on Garage - S3-compatible Object Storage alternative to Minio 2 months ago:
Minio has worked well for many years. Haven’t had any problems with it until now, but ready to migrate away.
- Submitted 2 months ago to selfhosted@lemmy.world | 16 comments
- Comment on Self-hosted Tools, Dead Tech, Papercrafting (Linux Prepper Podcast) 3 months ago:
If you want it as an article, here are the detailed show notes: …james.network/…/48-episode-8-shownotes-self-host…
- Self-hosted Tools, Dead Tech, Papercrafting (Linux Prepper Podcast on Fediverse)podcast.james.network ↗Submitted 3 months ago to fediverse@lemmy.world | 0 comments
- Comment on Self-hosted Tools, Dead Tech, Papercrafting (Linux Prepper Podcast) 3 months ago:
Good to know. I’ve actually been using the tools I discuss on the show, as opposed to only naming off whatever is the newest thing without having actually used it. Good to know if that isn’t clear.
Linux Prepper is related to doing everything myself with fully open tooling as much as possible. I’ve never seen another show do the same, so I thought it would be fun to try. Self-hosting everything, and using foss tooling for everything all the time, might not be practical, but it is a fun challenge. That is the intention.
- Submitted 3 months ago to selfhosted@lemmy.world | 4 comments
- Comment on Makerspaces, Conferences and Decentralized Storage 3 months ago:
Well, it is a podcast that is self-hosted and also focusing on self-hosting, Linux, DIY, and fully open source tools. My goal is to DIY everything possible using free and open tools. This episode is about going to a recent Linux conference, visiting a makerspace, and discussing distributed file shares of Tahoe-LAFS between a number of self-hosters.
- Comment on [deleted] 3 months ago:
What kind of work do you do? Curious since you don’t write by hand.
- Comment on [deleted] 3 months ago:
Do you scan or photograph such things?
