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
1 point

I deploy as much as I possibly can via Ansible. Then the Ansible code serves as the documentation. I also keep the underlying OS the same on all machines to avoid different OS conventions. All my machines run Debian. The few things I cannot express in Ansible, such as network topology, I draw a diagram for in draw.io, but thatโ€™s it.

Also, why not automate the certificate renewal with certbot? I have two reverse proxies and they renew their certificates themselves.

permalink
report
reply
1 point

This is the way

permalink
report
parent
reply
-4 points

psssst. ansible is red hat.

red hat bad.

permalink
report
parent
reply

What alternative to you suggest?

permalink
report
parent
reply

My reverse proxy can do automated renewal just fine. The SMTP relay requires a DNS challenge that is manual.

permalink
report
parent
reply
2 points

Why not have the reverse proxy also do renewal for the SMTP relay certificate and just rsync it to the relay? For a while I had one of my proxies do all the renewals and the other would rsync it.

permalink
report
parent
reply

It certainly wouldnโ€™t be because Iโ€™ve been doing it this way for so long that it never occurred to me. Nope. Certainly not that.

In fairness, I very recently switched from a cobbled together apache web server/rev proxy config Iโ€™ve been carrying along in some form for well over a decade (I remember converting the config to 2.4), to an NPM container. I had some initial trouble switching my certs over to NPM and havenโ€™t revisited that yet.

Iโ€™m in the middle of a major overhaul of my tech stack. Fixing certs is on my short list.

Thanks for pointing out where I was stuck in my ways.

permalink
report
parent
reply

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.5K

    Posts

  • 79K

    Comments