Selfhosted

53285 readers

1240 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

106

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

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

52 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

[–] philpo@feddit.org 2 points 4 hours ago (1 children)

Netbox,especially when combinded with Plugins is so incredibly good and might,that's it's almost funny how good it is. What I do Plugin wise:

Documents: not implemented yet by me,but one could store manuals,etc. directly within netbox.
Lifecycle and Inventory: While it's not as good as snipe-it (tbh, inventory is imho one of the worst plugins) it does the job for my small deployment
Slurp it to scan automatically
QR Code for obvious reasons
Floorplan as well

Of course that sounds overkill for a small deployment, but I simply forget too many things after a few months otherwise and it's something my family (wife is in IT and far more qualified than me) would need if something happens to me,so a proper documentation would be essential for that as well.

[–] dbtng@eviltoast.org 2 points 4 hours ago* (last edited 4 hours ago)

Alright already! I'll work on my upgrade.
I'm wondering if I should just build a new docker and then migrate the data instead of upgrading in place. I bet that's the easier thing to do in the end. Sounds safer too. I got backups and all, but ...