Selfhosted

53187 readers

1666 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

103

How should I properly document my homelab? (sopuli.xyz)

submitted 2 days ago* (last edited 2 days ago) by enchantedgoldapple@sopuli.xyz to c/selfhosted@lemmy.world

49 comments fedilink hide all child comments

Reading earlier comments in this community made me consider documenting the workings of my homelab to some extent, ie. docker configuration, credentials, ports and links of my services. I've tried to make it consistent and organised but it still feels half baked and insufficient. Everyone suggests documenting everything you do in your homelab but don't state how. Since I've hardly had experience running my own server, I would really appreciate observing the blueprint of some other fellow selfhoster for copying or taking inspiration from rather than considering documentation to be 'left as an exercise for the reader'.

Edit: I already have a note-taking solution with me. What I wish to ask is to know what needs to be documented and what the structure of the documentation should be to accommodate the information.

you are viewing a single comment's thread
view the rest of the comments

[–] comrade_twisty@feddit.org 31 points 2 days ago* (last edited 2 days ago) (2 children)

Everyone will have their own system.

I save all my credentials in Bitwarden/Vaultwarden and take notes in Joplin.

The good thing about YOUR homelab is that YOU’RE taking notes solely for YOURSELF and only YOU know how YOU work and how YOU organize YOUR thoughts.

[–] MonkeMischief@lemmy.today 2 points 9 hours ago (1 children)

The good thing about YOUR homelab is that YOU’RE taking notes solely for YOURSELF and only YOU know how YOU work and how YOU organize YOUR thoughts.

Normally I'd agree, in that it's not some corporate production environment, but also I personally want to document my self hosted setup in a kind of document that can at least be accessed and understood by my closest family, if something were to happen to me.

Convincing them to archive stuff on my Nextcloud instance for example, and them losing access because I'm not around, temporarily or permanently, would spoil the whole point of the endeavor.

[–] comrade_twisty@feddit.org 3 points 9 hours ago* (last edited 8 hours ago)

I‘m a realist in that regard, once I am gone all my hard work will go to shit in 6-12 months no matter how much I train an instruct my friends and family. They just don’t care enough to put in even a little bit of work.

[–] irmadlad@lemmy.world 7 points 2 days ago

I save all my credentials in Bitwarden/Vaultwarden

Yeah, I don't put key phrases, passwords, etc in my notes.