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

Would you be into a little bit of raping at a 9? Or is that just “I love kids in a non-creepy way”

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.

Ah, that makes sense. If only straight lines were the norm 😁

What does the electrician need to get up there for? It looks to me like that is already done. I’m not saying you’re wrong just that I think caulk is the best you can do to finish it out from this point both in terms of finished look and ease of removal in the future. Of course it would be better if you had a square and plumb room to work with but that ship has long since sailed.

Caulk is removable

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.

I’m gonna shove something in your gap but it ain’t a pillow

I think part of the reason some of those people live that way is because they don’t think through the effects of everyone else living their lives that way. Perhaps the stat boost to INT would give them the ability to follow that course of action to it’s logical conclusion and therefore choose to live differently?

I gave up on 343 more than a decade ago. Halo died the moment Bungie stepped away from it

It’s always been that way. Even most people who used the internet “way back when” have no clue how it actually functions. Terms like DNS and IPv4 are vaguely familiar concepts at best outside of professional or hobbyist circles.

There’s nothing inherently wrong with that either. There’s too much stuff for any one person to know. You learn the stuff that interests you and ignore the rest, which hopefully means somebody is interested in all of it. That’s why it’s good that there’s all different kinds of people out there.

I do, but unfortunately the dog just refuses to shit on the wall

In this case… I’ll allow it

Same. I’m working on electrifying everything. I have geothermal HVAC, a heat pump water heater, and an EV running off the solar panels. Only the gas stove remains.

There’s petabytes of free porn on the internet and yet tons of weirdos pay for subscriptions to porn sites. Such is life

Dan said he’s looking for a gf. I’m sure Will is nice but he’s not invited

I don’t. I hope they ship his body to every city in America like they do with ancient Egyptian kings, except instead of learning about history we take turns pissing in his mouth

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.