• 0 Posts
  • 189 Comments
Joined 3 years ago
cake
Cake day: July 3rd, 2023

help-circle

  • krashmo@lemmy.worldtoSelfhosted@lemmy.worldI've been busy
    link
    fedilink
    English
    arrow-up
    2
    ·
    2 days ago

    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.














  • 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.




  • I think that any solution in the form of a formal government regulation will be subject to that kind of corruption, and real solutions need to be found elsewhere.

    I think that’s a fair statement as it relates to the current US government but I don’t think that’s a valid general philosophy. I agree that our current priority should certainly be to implement a government that can be trusted to regulate things effectively. If that isn’t taken care of first then the rest doesn’t matter. As evidenced by, well, everything happening right now haha. Still, the ultimate goal should be government action on this topic because we cannot solve the problem at an individual level. Some people can have better outcomes than others but there’s no level playing field without government intervention.