The fourth article in my series about “self-hosting for newbies” explaining how I take care of backups for my YunoHost server.

  • irmadlad@lemmy.world
    link
    fedilink
    English
    arrow-up
    1
    ·
    6 months ago

    Tough crowd. I used Yunohost back in the day. I thought it was pretty good. Great for someone who is just starting out. It has evolved, and I think the newest version boasts the largest app catalog in it’s class.

  • atzanteol@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    0
    arrow-down
    1
    ·
    6 months ago

    In part one, I explained why I’m passionate about self-hosting and I discussed what you need to get started on this journey (a VPS and a domain name)

    You didn’t need either of those things. This reads like an ad for yunohost.

    • Rimu@piefed.social
      link
      fedilink
      English
      arrow-up
      0
      ·
      6 months ago

      No, it’s legit. Elena has been tooting and peertubing about the fedi and her self hosting journey for over a year.

      • atzanteol@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        0
        arrow-down
        1
        ·
        6 months ago

        It still reads like an ad for yunohost…

        I think one of the mistakes many newb self hosters make is thinking of systems in their entirety rather than as components.

        “How to install pihole on a raspberry pi” and “how to setup nextcloud on yunohost” are examples. All using very specific tools and very specific steps.

        I’m noticing this more and more with documentation for apps where they tell me to use their specific docker-compose file and have instructions to use let’s encrypt in a specific way rather than referring you to let’s encrypt as an option and pointing you at their docs.

        People aren’t learning how to use each of these tools and how to be flexible in their implementation.