I tried earlier today and I had no luck actually getting an instance running

It would help if the explanation was specific to a raspberry pi

  • Illecors@lemmy.cafeEnglish
    282·
    1 year ago

    Do yourself a favour and don’t host it, yet. Lemmy is not quality software. You have 3 options here:

    • pay someone to take care of it for you
    • learn more about computer management and computers in general, first; then host it
    • ignore the first two options, which will inevitably lead to your instance crashing and burning

    Best of luck!

      • caseyweederman@lemmy.caEnglish
        3·
        1 year ago

        I mean… You’d learn so much. Crash and burn maybe, but call it a win for all the knowledge you gain in the process.

      • dap@lemmy.onlylans.ioEnglish
        2·
        1 year ago

        Crashing and burning (in a non-production environment) is an excellent motivator to develop necessary skills; being unafraid to break things and fix them when they inevitably break helps you get a deeper understanding of how the systems work, for what it’s worth.

  • PeachMan@lemmy.worldEnglish
    201·
    1 year ago

    Agree with others here. Ansible isn’t for beginners and neither is a Lemmy instance.

    Try some other projects first, maybe some docker containers that involve a reverse proxy.

    For example, NextCloud is a very useful thing to set up as a project, but I would say that you specifically need the new Pi 5 with plenty of RAM for that. The Pi 4 doesn’t handle a full NextCloud installation well.

      • PeachMan@lemmy.worldEnglish
        61·
        1 year ago

        Oh yeah I think so. Honestly NextCloud is slow on any platform, so don’t be surprised if you’re not impressed. But it’s a neat project to set up.

  • zerodawnAEnglish
    14·
    1 year ago

    As a self taught self-hosting enthusiast i wouldn’t recommend ansible to a beginner. I know that sounds backwards as absible makes everything easy and does all the work for you but that’s also part of the problem. It would be like jumping behind the wheel of a self driving car without knowing how to drive at all. When (not if) something goes wrong it could go wrong hard and you’d lose the whole instance.

    It’s better to start with some other self hosted projects that interest you to get a feel for the process and software like docker then work your way up to bigger things like lemmy. I consider myself fairly versed in the process and lemmy still gave me some issues to set up and my pixelfed instance still won’t federate despite my best efforts. I’m pretty sure i know the issue, i just need to get around to fixing it.

    Last thought, the raspberry pi is a pretty impressive little pc for it’s size and price point but you might find yourself quickly burning through resources depending on the number of active users you have and how heavily you use it.

    • zerodawnAEnglish
      5·
      1 year ago

      Learning how to use your pi to run a reverse proxy to a self hosted blogging site would give you plenty of hands on starter experience. Run docker and portainer and mess with docker config files from a webgui to see what work and what doesn’t.

    • atzanteol@sh.itjust.worksEnglish
      3·
      1 year ago

      I agree completely with self hosting lemmy for a beginner. But disagree completely about ansible.

      Learning to script your environment is extremely useful for stability, maintainability, and security.

    • arudesalad@sh.itjust.worksOPEnglish
      1·
      1 year ago

      Could you give somd examples of something to selfhost? I am only really aware of selfhosting lemmy and other fediverse stuff

      • Midnight Wolf@lemmy.worldEnglish
        3·
        1 year ago

        So, I’m not new to this (omg it’s been 6+ years now wtf) but I don’t host a lot of stuff, and it’s been pretty easy to poke at; I’ve got:

        • plex
        • minecraft (bedrock and java)
        • freshrss
        • rustdesk
        • home assistant
        • vaultwarden
        • pihole
        • actual (budget software)

        Running in docker containers, along with a few of the built-in plug-and-play services on my nas. Of that list, plex, minecraft, freshrss, rustdesk, and vaultwarden were very easy to setup in my situation. Rustdesk is a really good remote control program/service, vaultwarden is a fork of the bitwarden server, and plex was almost comically simple to get going as a media host.

        • CosmicApe@kbin.social
          2·
          1 year ago

          I’m still getting my pieces together for my first server but I’m definitely gonna look into actual!

      • zerodawnAEnglish
        1·
        1 year ago

        You could set up a dns based ad-blocker like pihole and a vpn like wireguard to tunnel your phone back into your home network so you have ad-blocking on the go, too. That’s a semi beginner protect with plenty of tutorials to pick from.

        You could run nextcloud, syncthing, or immich to make your own cloud at home but that might need more than a basic pi setup.

          • zerodawnAEnglish
            1·
            1 year ago

            It’s a great software to run. I like to watch youtube tutorials that explain things step by step so i can understand what happens. If i find a good video i’ll see what other software that channel may have a tutorial on and if that software may interest me.

      • RCTreeFiddy@lemmy.worldEnglish
        9·
        1 year ago

        And which step in this process did you get stuck, and what were the errors, if any?

        You gotta give us some more info here.

        • arudesalad@sh.itjust.worksOPEnglish
          1·
          1 year ago

          Step 7. I dont have the errors now but I don’t think I had ansible or ssh set up correctly

          I dont really understand it as this is the first thing I am trying to selfhost other than a minecraft server.

          • RCTreeFiddy@lemmy.worldEnglish
            6·
            1 year ago

            SSH may be installed on the pi but may need to be enabled. That was the second to last bullet point in the requirements. The final on being to install Ansible. If you did not get the requirements taken care of, installation will not be successful.

            Please first try to SSH into your pi. Once you have that done, you should install Ansible. After that, you should be able to run the playbook from step 7 and we can proceed from there.

              • RCTreeFiddy@lemmy.worldEnglish
                13·
                1 year ago

                I’m not trying to be mean, but I think you might be trying to jump straight into the deep end before learning to swim. While the commands have been included in the guide in order for you to be able to install this, it really does help to understand what those commands do, and what they mean. I suggest first getting to know your pi a little bit better, learning how to get SSH going on that and then moving on to installing Ansible. There’s information on the raspberry pie website on how to get SSH enabled on your pi.

  • Decronym@lemmy.decronym.xyzBEnglish
    3·
    1 year ago

    Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I’ve seen in this thread:

    Fewer Letters More Letters
    DNS Domain Name Service/System
    IP Internet Protocol
    SSH Secure Shell for remote terminal access

    3 acronyms in this thread; the most compressed thread commented on today has 2 acronyms.

    [Thread #378 for this sub, first seen 27th Dec 2023, 03:35] [FAQ] [Full list] [Contact] [Source code]

  • brenno@lemmy.brennoflavio.com.brEnglish
    1·
    1 year ago

    I host it in a Truenas BSD Jail, and the process was as straightforward as compiling and running any other Rust / Postgres project. Which error did you get?