112
How do you document your setup? (piefed.social)
submitted 7 months ago by to c/selfhosted@lemmy.world
86 comments fedilink hide all child comments
 

Like soup-to-nuts. I know I need to document what I'm doing and I've started several times, but then I never go back and make updates. I don't know if it's just the ADHD or if I'm just going about it or thinking about it in the wrong way.

So I'm curious about:

  • what you use for your documentation
  • how you organize it
  • what information you include
  • how you work documentation into your changes/tinkering flow

Edit: Dang, folks! You all have given me a lot to read through, think about, and explore. Thank you!

you are viewing a single comment's thread
view the rest of the comments
[–] 1 point 7 months ago

I keep everything I do as minimal as possible.

Everything is documented using either sh scripts or markdown style plain text files. If I need anything more than that, I'm over complicating things for my brain.

The upside to this approach is that it works anywhere because it's all just text files and it's very tiny in size. I am more interested in making low-power/low-spec things work so less is appropriate.

  • permalink
  • fedilink
  • source
    •