• 5 Posts
  • 346 Comments
Joined 2 years ago
cake
Cake day: April 27th, 2024

help-circle



  • Eh… Not really. Qemu does a really good job with VM virtualizarion.

    I believe I could easily build containers instead of VMs from the nix config, but I actually do like having a full VM: since it’s running a full OS instead of an app, all the usual nix tooling just works on it.

    Also: In my day job, I actually have to deal quite a bit with containers (and kubernetes), and I just… don’t like it.



  • Zero.

    About 35 NixOS VMs though, each running either a single service (e.g. Paperless) or a suite (Sonarr and so on plus NZBGet, VPN,…).

    There’s additionally a couple of client VMs. All of those distribute over 3 Proxmox hosts accessing the same iSCSI target for VM storage.

    SSL and WireGuard are terminated at a physical firewall box running OpnSense, so with very few exceptions, the VMs do not handle any complicated network setup.

    A lot of those VMs have zero state, those that do have backup of just that state automated to the NAS (simply via rsync) and from there everything is backed up again through borg to an external storage box.

    In the stateless case, deploying a new VM is a single command; in the stateful case, same command, wait for it to come up, SSH in (keys are part of the VM images), run restore-<whatever>.

    On an average day, I spend 0 minutes managing the homelab.











  • Lmao. Lmfao, even.

    Here, I’m gonna save you some time and summarize the article for you:

    • everyone is talking about how good LLMs are [citation missing], but they’re missing the point!
    • because really, we’re already so much further ahead! There be magic tools out there!
    • wait, you want to know which ones? Uuuuh sorry, the people building then are keeping them a secret…
    • …because they are just THAT FRIGHTENINGLY GOOD! [citation missing]
    • seriously, I used one of them to build a 30k/month product in 2 hours with zero coding!
    • I mean… A subset at least. Oh I also did not do any review, so no idea just how badly fucked it is. Ah, and I guess the price tag comes from the existing reputation and legal guarantees provided by the original tool, which obviously I also couldn’t replicate.
    • but worry not! I’m sure I’d be able to build the full tool in DAYS!
    • I won’t though. Even though it could TOTALLY make me 30k per month per user. Totally.
    • instead, I’ll PROVE to you JUST HOW GOOD these SECRET TOOLS are! Checkout this GitHub repo!
    • …ah, no, sorry, I misspoke. I’ll obviously NOT be using the secret, but TOTALLY REAL [citation missing] tools that this entire article is about. For some reason. They’re totally real though bro. Trust me bro. I’m sure one more data-center will fix it bro. Just need to prompt right bro. Like bro, people don’t realize how gooooooood LLMs are bro. I swear bro. My prompts are so good I need to keep them secret because it’s SCARY bro. Bro.

    Ahem. Maybe I editorialized a tiny bit. Not much though, trust me bro.





  • That’s what I’m not so sure about though. Forgejo/codeberg/… projects are already not hard to find through search engines. Add a federated in-forgejo search and you’d be set there.

    And currently the problem indeed is that a forgejo project is on instance X, and you, as a developer only have accounts on Y and Z. But through federation, that would stop mattering, so I don’t get the “it’s where contributors are”: as long as contributors have a single forgejo account anywhere, we’d be good.