In all honesty, it is a hodge podge. Some are in my dokuwiki, some are plain text, some are markdown, some in my phone, lots on scraps of paper. Just about the time I get it all in one place I scrap my systems and start over.
this post was submitted on 28 Jul 2023
137 points (95.4% liked)
Selfhosted
40323 readers
655 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 1 year ago
MODERATORS
I'm kinda like that too. But I'm redoing my setup and I wanted to try and redo the way I document things. Or at least try.
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)
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.
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.
load more comments
(8 replies)
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. :)
Why not push it up to GitHub? Then you also get a commit history to see your changes overtime.
Wow that sounds convinient, where can i find a guide describing this? Has zero experience with git 😅
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!
load more comments
(1 replies)
load more comments
(1 replies)
I'm using anytype.io, it's been pretty neat so far.
I have a git repo for it, needless to say. And so README.md plus a network diagram from https://app.diagrams.net/
I run a local MediaWiki appliance from turnkeylinux, super easy to spin up in proxmox.
Hackmd.io for simple markdown docs.
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.
I document steps for configuration or installation of a service. Normally, only if it's not pretty obvious and I have to combine multiple sources to figure out what I need to be doing.
I also document all of my static IP address in one place. That way I know which service is on which IP and I have a list of used IPs so I don't try to reuse them.
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