Little bit of everything!

Avid Swiftie (come join us at !taylorswift@poptalk.scrubbles.tech )

Gaming (Mass Effect, Witcher, and too much Satisfactory)

Sci-fi

I live for 90s TV sitcoms

  • 11 Posts
  • 178 Comments
Joined 1 year ago
cake
Cake day: June 2nd, 2023

help-circle




  • Exactly right there with the not worrying. Getting started can be brutal. I always recommend people start without worrying about it, be okay with the idea that you’re going to lose everything.

    When you start really understanding how the tech works, then start playing with backups and how to recover. By that time you’ve probably set up enough that you are ready for a solution that doesn’t require setting everything up again. When you’re starting though? Getting it up and running is enough



  • WD Red has always been my go-to, and in the last 8 years of homelabbing I haven’t had a single one fail. Blues and Greens are not build for NAS operations, and you’ll see them fail. Toshibas I haven’t had a single one make it past a year, except for their gaming drives.

    If you want the shortcut, the WD Elements usually go on sale at Best Buy regularly, and they’re always a WD Red or White, which will also work. All of my drives have been one of those. You just shuck the internal drive out of the enclosure


  • I do something similar to op, however, running llms is what finally convinced me to switch over to kubernetes for these exact reasons, I needed the ability to have gpus running on separate nodes that then I could toggle on or off. Power concerns here are real, the only real solution is to separate your storage and your compute nodes.

    What OP is suggesting is not only not going to work, and cause damage probably to the motherboard and gpus, but I would assume is also a pretty large fire hazard. One GPU takes in an insane amount of power, two gpus is not something to sneeze at. It’s worth the investment of getting a very good power supply and not cheaping out on any components.




  • I am a developer, you’re right. I think I’ll fork it and add my own ldap auth in. Good chance to learn Rust.

    I don’t like it because that’s exactly how things like this RealVNC thing happen. These companies all start with good will, we have a free tier, we are open source, we love the community. Then one day they snap it all back, say “Hey we never said it’d be forever, did you look in subsection 6 of section 42? It said in there that your license wasn’t a license and now you need to pay up” So yeah, especially in context of RealVNC I’m real jaded against “good will companies”.

    You want to charge for your product? Super, do so. Don’t lie and say you’re doing good and then rip it out later. Gitea is a good example of that.




  • That’s really funny because I am in that position at work where I can make suggestions - or throw down the ban hammer.

    I’ve successfully migrated 3 companies away from Google Cloud because of my horrible personal experience with them. There are so many products I’ve used that have been great and others terrible. You’re exactly right, that’s why individual free tiers existed - to encourage us to try them to push them at work.



  • I use teamviewer to access a relative’s computer when she needs help, and it’s the same nagware. Like okay, I understand there are cloud costs. But where exactly are they here? I am a row in a database, you store my credentials and probably a couple of keys. All data is between the host computer and me, there’s no processing of any kind there. Why exactly should I pay you monthly? There’s no value benefit.




  • Just jump in tbh. Choose one service you want to try, get it up and running, and play with it

    Few bits of advice I have is to plan that you will tear it down a few times. Couple of reasons. One, that way you don’t have to plan to have it perfect the first time. Play with spinning up a VM/container, installing stuff, getting something working, without the stress of needing it to be perfect. Second, because it’s good to know how you did something and know you can repeat it.

    Write everything down as you go. For me, I made a huge readme to keep track of things I did, again this helps with if you fuck up you can always redo it. Trust me, this will save you. Readme in git, Google docs, something you can reference when everything is down.

    Finally, DO NOT choose something your first time that is open to the public. Start small. Something private like Plex/jellyfin, or tandoor, something just for you. Public services are a can of worms. Maybe you want to start with Lemmy, but work up to it. For more obvious reasons like you have an expectation of uptime and you need monitoring, which will require knowledge of all of that, but also more nuanced reasons, like, we’ll do you know how to register csam? Because I didn’t know the process until I started hosting services for the public. Just don’t for now. Hold off until later.

    Anyway, hope that helps! Have fun, and don’t be afraid to fail. Remember, we can’t ever plan not to fail, but if we must fail, fail fast



  • Very cool! Thanks for posting this. Minio was great, but they started tailoring to enterprise clients, and it’s become more and more annoying to keep it running in a homelab. (Security is 100% a great thing, but forcing high levels of security on me when I’m running 2 containers in a compose stack, where the minio container will never have exterior access… eh, I just gave up). So, I’m happy there’s one tailored a bit more towards self hosters