• 0 Posts
  • 40 Comments
Joined 2 years ago
cake
Cake day: October 6th, 2023

help-circle











  • My successful path for homelab stuff is to use kubernetes (k3s locally and digital ocean DOKS for cloud resources) with argocd and gitops. Everything I change is via a git commit+push so I can always rollback, and if this machine dies, once I replace/repair the hardware I can pull all backed up content from object storage, install K3s again, reconfigure the authentication for Argocd, and it will repopulate all the running services.

    I am absolutely not saying this is the right path for you as I came into nearly all my modern knowledge through my career, but it is a path


  • Instructions that start with “open terminal” are then followed by text commands to execute, all of which can be broken down and dissected to learn exactly what they are doing and why they are there. And generally, CLI tools, config files, etc have a very stable interface that doesn’t change much over time (generalizing broadly; obviously there are some softwares with major changes which this does not apply to). Ultimately, they can be replicated very easily with copy/paste by the end user.

    Instructions that are just a bunch of screenshots are subject to user error and whims of the softwares UI designers and your own personal look and feel settings.

    Instructions that are “download this file and execute it” are how you fuck up your system with a difficult, possibly nonexistent, path to recovery.

    So, I’d advise to get comfortable with the terminal and accept those instructions as the blessing that they are