Or maybe a two click solution? :)

  • Disregard3145@lemmy.worldEnglish
    7·
    1 year ago

    Self hosting what?

    In general

    1. Install docker
    2. Copy and paste docker run commands from the getting started guide
    3. Learn from mistakes
    • aeternum@kbin.social
      2·
      1 year ago

      It’s so easy to self host these days. I remember when you’d have to fuck around with Apache configs and fuck around with app config files etc. Now you just run docker. It’s so great these days!

      • zib@kbin.social
        2·
        1 year ago

        I’m still fucking with the apache configs (I fucking hate apache…). As someone with no docker experience whatsoever, are there any getting started guides you would recommend for someone looking to make the switch?

        • aeternum@kbin.social
          1·
          1 year ago

          I don’t have any specific guides in mind, but you’ll want to use docker-compose as much as possible, also create /home/your_user/docker/app/ for each app, and keep your docker compose files. If you use docker run, keep a copy of the commands you use, because if you need to restart your services, it will be a lot easier than having to search up the command in your bash history again. You can just cat docker.txt | bash and it will recreate your docker containers for you. That’s all i can really think of for getting started. Also, docker ps will be a godsend.

    • JTR@lemmings.basic-domain.comEnglish
      1·
      1 year ago

      To be fair thats pretty much the IT gig in general, not the docker part but the rest copy/paste run commands, then learn from whatever you screw up couple of years later you might very well end up working in IT

      • snekerpimp@lemmy.worldEnglish
        1·
        1 year ago

        docker-compose helped me wrap my head around docker. I can use run commands now, but prefer to either modify a compose file or create my own to spin things up.

    • sentient_loom@kbin.social
      1·
      1 year ago

      Okay. I keep reading about docker. What’s the difference between a docker and just installing an app on rented server space?

      Does each dock (?) have its own server? (Apache or nginx or whatever?)

      Does each dock host a whole site, or do you have a dock for your database and a dock for your web app?

      • TooTallSol@kbin.social
        3·
        1 year ago

        What’s the difference between a docker and just installing an app on rented server space?

        Functionally? Not much. But people who selfhost typically want everything on computers they own. Whether it’s for learning purposes, or to not have their stuff on “someone else’s computer” selfhosting usually means you’re running software on computers you own, almost always within your own house.

        Does each dock (?) have its own server? (Apache or nginx or whatever?)

        Each docker image usually has a web server built in. The philosophy of docker is that it contains everything needed to run the app. Even a small linux OS (LibELEC or Alpine are favorites for docker images). So while you’re not managing the web server in a docker image each docker image will have its own web server if web access is needed

        Does each dock host a whole site, or do you have a dock for your database and a dock for your web app?

        Docker the program is what runs all the docker images on a computer. Each docker image is built as per the software’s developer. Some docker images will have a web app and a database combined into a single image, while others will expect a separate database server running independent of the image (It won’t care if the database server is a docker image or not; just that it has access)

      • soft_frog@kbin.social
        1·
        1 year ago

        Docker is basically a virtual machine image you write your software in. Then when you run the software you don’t need to worry about compatibility or having the right dependencies installed, it’s all included in the docker image.

        Think of Docker as being Nintendo cartridges that you can take to any friends house, plug them in, and play. Servers can run more than one Docker container.

        The approach greatly simplifies writing code and having it work on your server, reduces errors, and adds a layer of security.

  • hitagi@ani.socialEnglish
    1·
    1 year ago

    I think you should just choose whatever software or project you want to selfhost, read how to do it, and learn by doing.

    I’m a complete idiot but I learned how to self host from trying to set up a Jellyfin server on my Windows desktop. Now I host game servers, Matrix with bridges, Discord bots, and this Lemmy instance that I’m in. I (re)learned how to use Linux and fell in love with it too.

    It’s all about reading the manual I guess.

    • BetterNotBigger@lemmy.worldEnglish
      1·
      1 year ago

      This is how I got a career in Software Engineering, literally had a strong motivation to build a clan website for my Counter-Strike 1.6 crew and I just ended up learning by maintaining self-hosted websites, forums, and voip. Kept doing it over and over by building other projects and then realized people pay for this skill…

  • Gompje@lemmy.worldEnglish
    1·
    1 year ago

    Hmm maybe Unraid with the community store? When you got unraid running its just a matter of selecting an app from the store and hop: it runs. Kinda…

  • zaggynl@lemmy.worldEnglish
    11·
    1 year ago

    You could go through the following route:

    • purchase something like a small Synology NAS and learn how to set up the networking/firewall bits
    • buy/repurpose a used desktop/laptop, install something like yunohost/unraid
    • buy parts for your own server, put it together, use the same own server but install proxmox, setup VMs/containers
    • use the same own server but install debian, play around with docker/docker-compose/ansible

    If you don’t have the means to get new hardware, you can use hyper-v or virtualbox for free on Windows or virtualbox/virt-manager on Linux on existing hardware.

    Simple project to start with: install pihole and configure it as your DNS adblocking filter at home

    • install iphole on a VM/PC/raspberry pi that is connected to your home LAN
    • configure your PC or router to use the pihole host as DNS server
    • test various websites you know that have ads before and after using pihole

    While doing things like these, keep notes what you do by day, using those notes, put together your own howto manuals. Do not be afraid to fail, sleep over it and try again, don’t be afraid to ask specific questions here or on other forums, IRC.

      • webghost0101@lemmy.fmhy.mlEnglish
        1·
        1 year ago

        Is it basicly a docker alternative? I know enough to have gotten some servers running in ubuntu docker containers but if i want a lemmy instance then that would be a first time exposing it trough the web.

        Is it is as simple as just opening the right port?