this post was submitted on 28 Jul 2023
137 points (95.4% liked)

Selfhosted

42631 readers
423 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:

  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!

founded 2 years ago
MODERATORS
 

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.

(page 2) 50 comments
sorted by: hot top controversial new old
[–] rentar42@kbin.social 3 points 2 years ago (1 children)

I know that I would keep forgetting to update the docs, so my documentation are the ansible playbooks and docker-compose.yaml files that I use to set it all up.

That leaves anything that has to be done in some Ui undocumented, so I try to keep that to a minimum, which isn't always easy (I'm looking at you authentik!).

load more comments (1 replies)
[–] antony@lemmy.ca 3 points 2 years ago

I use Ansible, Docker, and Emacs OrgMode files committed to Git. Diagrams are a mix of Miro and Graphviz. There's also a few markdowns in there too. Joplin is used for rough notes only.

[–] markr@lemmy.world 2 points 2 years ago (1 children)

I use bookstack. Simple selfhosted wiki.

load more comments (1 replies)
[–] happyhippo@feddit.it 2 points 2 years ago* (last edited 2 years ago)

I have a git repo for it, needless to say. And so README.md plus a network diagram from https://app.diagrams.net/

[–] kurt_propane@lemm.ee 2 points 2 years ago (2 children)

Why not push it up to GitHub? Then you also get a commit history to see your changes overtime.

[–] ZebraGoose@sh.itjust.works 2 points 2 years ago (2 children)

Wow that sounds convinient, where can i find a guide describing this? Has zero experience with git 😅

[–] cpo@lemmy.world 2 points 2 years ago

There are tons of tutorials around, but the basic gist is that you only use a couple of commands (or even a good frontend) in git, especially when it's a one (wo)man show.

I highly recommend it!

[–] kurt_propane@lemm.ee 1 points 2 years ago

Gotcha. Git is useful in so many way, but it can be confusing to learn. I don’t have a guide on hand but searching for ‘getting started with git’ will get you pretty far.

Another great way to do this that I just thought of this second is using Notion. It is in markdown.

load more comments (1 replies)
[–] Johnny5@lemm.ee 2 points 2 years ago* (last edited 2 years ago)

I run a local MediaWiki appliance from turnkeylinux, super easy to spin up in proxmox.

[–] grimer@lemmy.world 2 points 2 years ago

Any chance you wouldn't mind sharing the SSL renewal doc? Redacted of course. Mine is coming up and I'd like to do it correctly this time. :)

[–] gobbling871@lemmy.world 2 points 2 years ago (1 children)

Comments inside the docker-compose.yml files?

load more comments (1 replies)
[–] ludw@lemmy.world 2 points 2 years ago

I'm using anytype.io, it's been pretty neat so far.

[–] Kcg@lemmy.ml 2 points 2 years ago

Hackmd.io for simple markdown docs.

[–] dr_robot@kbin.social 2 points 2 years ago (4 children)

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.

[–] ttk@feddit.de 1 points 2 years ago (4 children)
load more comments (4 replies)
load more comments (3 replies)
[–] ComptitiveSubset@lemmy.world 1 points 2 years ago (1 children)

I write down everything I built so for plus future plans in OneNote. This kind of defeats the purpose of self hosting but I want to keep a written copy complete off site in case if a complete loss. Plus I like OneNote. It’s actually a well designed product. Scripts, docker compose files and such are in GitHub.

I won't argue. I do think OneNote is a good product and I use it a lot for work.

[–] pound_heap@lemm.ee 1 points 2 years ago

Some stuff is in Joplin, some stuff is in wiki.js. Joplin lacks organization features. Wiki.js stores stuff in database and has problems with search, both are possible to fix, I believe...

Occasionally I remember about problems with this setup, but I'm too lazy to fix or replace it

load more comments
view more: ‹ prev next ›