My home lab has a mild amount of complexity and Iโ€™d like practice some good habits about documenting it. Stuff like, what each system does, the OS, any notable software installed and, most importantly, any documentation around configuration or troubleshooting.

i.e. I have an internal SMTP relay that uses a letsencrypt SSL cert that I need to use the DNS challenge to renew. Iโ€™ve got the steps around that sitting in a Google Doc. Iโ€™ve got a couple more google docs like that.

I donโ€™t want to get super complicated but Iโ€™d like something a bit more structured than a folder full of google docs. Iโ€™d also like to pull it in-house.

Thanks

Edit: I appreciate all the feedback Iโ€™ve gotten on this post so far. There have been a lot of tools suggested and some great discussion about methods. This will probably be my weekend now.

You are viewing a single thread.
View all comments View context

Selfhosted

!selfhosted@lemmy.world

Create post

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:

  1. Be civil: weโ€™re here to support and learn from one another. Insults wonโ€™t be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Donโ€™t duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (donโ€™t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

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

Questions? DM the mods!

Community stats

  • 4.8K

    Monthly active users

  • 3.6K

    Posts

  • 77K

    Comments