Self-Hosted Main

At work we use Logseq for notes and we store software licenses in vaultwarden.

I also have all of the docker compose files and other required files in a git repository with a readme per compose stack.

I've been wanting to build a system just like this for a while. I started just jotting down all the information in a wiki and then never found any benefit from building a more structured system that the simple wiki already provides.

Happy to discuss in further detail, maybe even talk about prototyping something basic if you have some good suggestions.

after googling my ass wound

say what now?

Take time to read/try/learn about Netbox, it should be perfect for you.

At Work, I deployed Netbox and, even if the teams were reluctant at first, they finally saw the benefits and slowly gave up their infamous excel sheets 😉

For general documentation and scripts, I tried to push people to MKdocs-material automatically updated from a Gitea repository but people are too allergic to Markdown...

"After googling my ass wound" is not something I expected to hear today, but here we are

Probably not your case, but that's what I use for my homelab:

• OIDplus for keeping OIDs, IPs, .home.arpa subdomains etc
• local-only Wordpress as a knowledgebase. Today I'd probably chose Bookstack, but it did not exist 11 years ago....

https://www.bookstackapp.com/ Most of it resembles Confluence that is a popular documentation platform in the IT world...

I've used Dokuwiki in the past, but at the end of last year, I swapped everything to Notion. I have everything from SOP, licenses, Hardware DBs, and Network DBs stored in one place.

For creds, I store these separately in Bitwarden.

Check out the client management documentation for ITFlow.

https://docs.itflow.org/

It's modularized so you can turn off the parts you don't need, like accounting or ticketing.

Hudu , Docusnap, Gira.

We use Hudu, but for us it´s limited in function.

Anyone else ever heard of (or using) iTop?

So what we're looking at is probably two or three systems here. I can't help you on what systems integrate.

Documentation

This is for general documentation. SOPs, etc.

I generally advise documentation be stored in Markdown. This is after decades of having to migrate systems or being locked into a documentation system because a migration path was too timely.

Markdown is ultra portable and easy to store/backup. You can get change management interfaces for it, or store it in Git if you have to.

Even something like mdwiki would do the trick in a pinch. The value you see out of this lies in how well you keep it organized and how well you use it.

Client Secrets

This will be served by a secrets manager like https://github.com/Infisical/infisical

I've never used it but I've seen it recommended and it seems like a good project.

I've used things like KeePass, Bitwarden andOnePass. My preference would probably be none of them, but I do like Bitwarden for a personal vault.

Asset Management

This should be handled by an asset management system. This is for things like licenses, hardware, etc.

Snipe-IT was actually my pick for this. Just for assets though, nothing else.

Another vote for Bookstack. We've been using it in a business for years now. Easy to setup and configure. Easy to use. Just works.