Honestly, for those tools, I'd recommend posting in piracy@lemmy.dbzer0.com.
Echoing some other comments, those are decently complex tools all around. I'd recommend doing a few tutorials on docker before trying out that project (short ones, just to build a mental model).
As others have said, docker is a command line tool. docker -v in your terminal should be enough to "find" it. That'll show you the version of docker you have installed.
From there, I'd recommend the hello world image to start (this should get you there https://www.geeksforgeeks.org/docker-hello-world/).
From there, keep messing with it. Get more familiar with docker through their docs. Read a bit on images vs containers, port mapping, and volumes and mounts.
As others have said, look for docker only in the terminal. And then expect to spend a little time familiarizing yourself with what problem docker solves and how it solves it. Once you've got docker in your back pocket, you'll be very well situated to set up all kinds of apps.
And when you run into other problems, there's communities to answer and work through the issues
I'm assuming you mean the jellyfin server and not the Android TV client specifically.
Running the jellyfin server on an SBC is possible, I'm running it on a pi 4 right now. Personally, I'd recommend installing docker and running the service in a container. There's official docs for how to do so https://jellyfin.org/docs/general/installation/container/
That being said, Jellyfin docs recommend against running on an SBC. I too, running it on an SBC, recommend against it. It can do the "happy path" well. But if the stored media is in a format that requires the server to transcode it for the current, it cannot handle it. The time it takes to transcode is several times longer than the actual run time of the media. You will have a bad time. I'm currently looking to change/upgrade the hardware to work around this
I'm not totally sure I get what you're saying in 2, but I appreciate your endorsement of quick sync
Much appreciated. I was worried I'd need a graphics card. It's great to hear that some CPUs are overkill
Thank you. That's exactly the kind of answer I was looking for. It's good to know that this is just a struggle for the pi and not something CPUs as a whole have an issue with
Hey all, I started hosting my own media server using jellyfin on a raspberry pi. This was mostly because I was new to the space and didn't want to invest heavily in hardware only to drop the project or find that I couldn't make it work for some reason.
I've now got it all set up and working, but the pi is absolutely not able to handle any sort of transcoding. So I'm now looking to upgrade the hardware.
Currently, I only need something that can handle transcoding two sub-4k streams concurrently. But I don't want to fully shut away the possibility of streaming 4k media. I should have the space for it, my current limiting factor is processing power.
Reading the jellyfin docs on recommended hardware, my understanding is that I should be OK if I get a recent Intel i7 CPU as long as it's got integrated graphics?
I am currently planning to build a small form factor PC and run it as a headless Linux (possibly Debian) server with jellyfin and everything else running in docker.
Mostly, I want to ask: does anyone with experience doing this have concerns or advice? In particular:
-
Is just the CPU processing power sufficient for everything if the CPU is chosen correctly?
-
If the CPU is not sufficient, is it difficult to set up a dedicated graphics card on a headless server?
Is there a place to get some of the clips they've got of Alex?
In particular, I want the "humans are born (made?) to hype?" clip to play whenever I'm tempted to upgrade my phone or whatever. I feel like the clip will snap me back to reality in a uniquely effective way
Googling off of this response, I think you're right that an NAS is the best solution long term. And in terms of a fully scalable system, I saw that I can create a Distributed File System of multiple NAS systems to even further scale. So thank you
I'm just getting started on my first setup. I've got radarr, sonarr, prowlarr, jellyfin, etc running in docker and reading/writing their configs to a 4TB external drive.
I followed a guide to ensure that hardlinks would be used to save disk space.
But what happens when the current drive fills up? What is the process to scale and add more storage?
My current thought process is:
- Mount a new drive
- Recreate the data folder structure on the new drive
- Add the path to the new drive to the jellyfin container
- Update existing collections to look at the new location too
- Switch (not add) the volume for the *arrs data folder to the new drive
Would that work? It would mean the *arrs no longer have access to the actual downloaded files. But does that matter?
Is there an easier, better way? Some way to abstract away the fact that there will eventually be multiple drives? So I could just add on a new drive and have the setup recognize there is more space for storage without messing with volumes or app configs?
Assuming the best intentions, they could fully intend (and ideally be in the process of) returning your charger. They could just be asking to ballpark when your phone will be at full charge so they can ask to use the charger again later
Personally, I cannot recommend One Pace enough. I watched ~500 episodes of the officual show before it just became too much.
About 1/4 of each episode is theme and credits Another 1/4 is flashbacks or closeups to fill time
The story is GREAT but the show suffers from pacing issues hard.
One pace rips out the filler and gives the story the pacing it needs. The only drawback is that it takes time for the fans making it to produce (totally understandable). Personally, I'd recommend watching One Pace where available and reading the Manga for the parts they haven't completed yet.
I know people love the official show; there's a lot to love! But that's my two cents.
For educational purposes what is a more expected/desired response from a nuerotypical person?
I skimmed the guide you sent and the top says that the portions in brackets are placeholders and need to be replaced with real values. If you change {{ lemmy_docker_image }} to be the name of the image to use dessalines/lemmy:0.18.0 for example, do you get further
Huge respect for what you've built here, but it might be worth reaching out to the lemm.ee admin. I only know enough DevOps and cloud hosting to be dangerous, not helpful. But his instance seems stable and scalable. He might be able to offer some insight into the issues here