

Same. When I first started down that path I kept finding posts about how it was impossible to set up and maintain but it’s been pretty painless for me. I basically had no clue what I was doing and I figured it out just fine.


Same. When I first started down that path I kept finding posts about how it was impossible to set up and maintain but it’s been pretty painless for me. I basically had no clue what I was doing and I figured it out just fine.
That’s fine. If property rights don’t exist then there’s no legal basis to charge us with anything if we burn their houses and businesses down. We just need to make sure they’re unoccupied at the time.
There are certainly things you can do with a server at home that would be off topic for this community, right?
I don’t want to hear about hosting CSM but anything else is fair game imo


If you click through some of the options on this page: https://jellyfin.org/contribute/
It links to a donation option here: https://opencollective.com/jellyfin


If you use it weekly it shouldn’t be free to you, certainly if you use it more frequently than that. Give money to the projects you depend on or they will disappear.
Copy/paste from another comment I made a while back:
Look into docker containers in general. If I was going to start from scratch in your position this is what I’d do:
Install a Linux distribution on the computer you plan to use for self hosting. This can be anything from a raspberry pi up to a custom build but I would recommend starting with something you have physical possession of. I found Debian with the KDE plasma desktop environment to be pretty familiar coming from Windows. You could technically do most of this on Windows but imo self hosting is pretty much the only thing that a casual user would find better supported through Linux than Windows. The tools are made for people who want to do things themselves and those kinds of people tend to use Linux.
Once you have a Linux distribution installed, get docker set up. Once docker is set up, install portainer as your first docker container. The steps above require some command line work, which may or may not be intimidating for you, but once you have portainer functional you will have a GUI for docker that is easier to use than CLI for most people.
From this point you can find the docker installation instructions for any service you want to run. Docker containers have all the required dependencies of a given service packaged together nicely so deploying new services is super easy once you get the hang of it. You basically just have to define where the container should store it’s data and what web port you want to access the service on. The rest is preconfigured for you by the people who created the container.
There’s certainly more to be said on this topic, some of which you would likely want to look into before you deploy something your whole family will be using (storage setup and backup capability, virtual machines to segregate services, remote accessibility, security, etc). However, the above is really all you need to get to the point where you can deploy pretty much anything you’d like on your local network. The rest is more about best practices and saving yourself headaches when something breaks than it is about functionality.


Unless you’re doing that from a separate device in a separate location then all you’re doing is giving them the data they need to link those two accounts
That’s overly dramatic phrasing and you know it. Adding this kind of hyper technical quip to a thread aimed at beginners is insane. Stop doing that.
Look into docker containers in general. If I was going to start from scratch in your position this is what I’d do:
Install a Linux distribution on the computer you plan to use for self hosting. I found Debian with the KDE plasma desktop environment to be pretty familiar coming from Windows. You could technically do most of this on Windows but imo self hosting is pretty much the only thing that a casual user would find better supported through Linux than Windows. The tools are made for people who want to do things themselves and those kinds of people tend to use Linux.
Once you have a Linux distribution installed, get docker set up. Once docker is set up, install portainer as your first docker container. The steps above require some command line work, which may or may not be intimidating for you, but once you have portainer functional you will have a GUI for docker that is easier to use than CLI for most people.
From this point you can find the docker installation instructions for any service you want to run. Docker containers have all the required dependencies of a given service packaged together nicely so deploying new services is super easy once you get the hang of it. You basically just have to define where the container should store it’s data and what web port you want to access the service on. The rest is preconfigured for you by the people who created the container.
There’s certainly more to be said on this topic, some of which you would likely want to look into before you deploy something your whole family will be using (storage setup and backup capability, virtual machines to segregate services, remote accessibility, security, etc). However, the above is really all you need to get to the point where you can deploy pretty much anything you’d like on your local network. The rest is more about best practices and saving yourself headaches when something breaks than it is about functionality.


Yes, I said “in some way” because not everyone can contribute code directly. There are other things besides money you can offer to contribute (graphic design, community/brand management, communication, general organizational tasks, forum moderation, etc) but funding is usually the simplest and most necessary.


I need Linux phones to be a thing now more than ever.
This doesn’t happen in a vacuum. If you’re not already, find a project and contribute towards it some way.


They are more similar than they are dissimilar. Only uber nerds see the differences more prominently


Fairphone does partner with Murena for e/os. It’s pretty similar to grapheoneOS


Haha do what works for you. I was able to get into them after a long car trip where I forced myself to listen to an audiobook. After finishing it it got easier and easier the more I did it. Now I barely read physical books.


Not off topic at all. I have never heard of it but it sounds interesting. Thanks for the tip


Haha I get that. I was the same way for a long time but gave them another shot a year or so ago and now I’m hooked. They are so much more convenient than physical books


Nice, it sounds like you’re learning stuff just fine. I recommended it elsewhere in the comments here but if you’re looking for audiobook sources I suggest checking out libro.fm. They give half of your purchase price to a local bookstore of your choice and you can download the files in multiple formats with no DRM.


Libro.fm seems to be a solid paid service. They give half of your purchase price to a local bookstore of your choice and you can download the files in multiple formats with no DRM.


Set up audiobookshelf via docker. I like using portainer to manage docker containers because it has a GUI. Command line stuff is more difficult if you don’t have the background experience to go with it. I think doing it all in a GUI feels more comfortable for most people.
Docker can also be kind of intimidating if you are just wading into the self hosting world but it really is much simpler to use once you get the hang of it. Portainer helps a ton with that. Audiobookshelf would be great to start with both imo because it’s a pretty basic set up. You have to define a storage location for your library and config files and that’s about all it takes to get it up and running.
I recently got into all this and remember well what it was like to feel out of my element so feel free to ask questions if you have any. I’m no expert but I’m happy to share what I can.
Says the guy intentionally running a computer off a switched outlet and complaining about how hard that makes things