• 0 Posts
  • 153 Comments
Joined 1 year ago
cake
Cake day: June 15th, 2023

help-circle










  • cybersandwich@lemmy.worldtoLinux@lemmy.mlNixOS forked
    link
    fedilink
    arrow-up
    9
    arrow-down
    14
    ·
    2 months ago

    Wait so people got butthurt that a company made a deal with nix. That company also does business with ICE. And people are mad at Nix?

    What am I missing?

    Also companies and open source entities do business with all manner of government(s) all the time.


  • cybersandwich@lemmy.worldtoSelfhosted@lemmy.worldPost your Servernames!
    link
    fedilink
    English
    arrow-up
    4
    arrow-down
    1
    ·
    2 months ago

    “rocinante” for my proxmox host.

    “awkward, past his prime, and engaged in a task beyond his capacities.” From don Quixote’s wiki page.

    It seemed fitting considering it is a server built from old PC parts…engaged in tasks beyond its abilities.

    The rest of my servers (VMs moslty) are named for what they actually do/which vlan they are on (eg vm15) and aren’t fun or excitin names. But at least I know if I am on that VM it has access to that vlan(or that it’s segregated from my other networks).






  • I don’t have nearly that much worth backing up(5TB–and realistically only 2TB is probably critical), but I have a Synology Nas(12TB raid 1) and truenas (zfs striped/mirrored) that I back my stuff to (and they back up to each other).

    Then I have a raspberry pi with a USB drive (8tb) at my parents house 4 hours away, that my Synology backs up to (over tailscale).

    Oh, and I have a USB HDD(8tb) that I plug in and backup my Synology Nas to and throw in my fireproof safe. But thats a manual backup I do once every quarter or 6 months if I remember. That’s a very very last resort backup.

    My offsite is at my parents.

    And no, I have not tested it because I don’t know how I’m actually supposed to do that.




  • Breaking things is the best way to learn. Accidentally deleting your container data is one of the best ways to learn how to not do that AND learn about proper backups.

    Breaking things and then trying to restore from a backup that…doesn’t work. Is a great way to learn about testing backups and/or properly configuring them.

    The corrolary to this is: just do stuff. Analysis paralysis is real. You can look up a dozen “right ways” to do things and end up never starting.

    My advice: just start. If you end up backing yourself into a corner where you can’t scale or easily migrate to another solution, oh well. You either learn that lesson or figure out a way to migrate. Learning all along the way.

    Each failure or screw up is worth a hundred “best practice / how to articles”.