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
136 points (95.3% liked)
Selfhosted
50352 readers
406 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 2 years 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.
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!
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.
Seems a lot of people are doing that.
I have a git repo for it, needless to say. And so README.md plus a network diagram from https://app.diagrams.net/
I use logseq to record any manual steps as well as any administrative actions that I take on a service. That being said, all of my homelan infrastructure is codified and stored in git in various ways so, it can be recreated as needed. There are very few manual steps in reconfiguring any of my services.
I run a local MediaWiki appliance from turnkeylinux, super easy to spin up in proxmox.
Comments inside the docker-compose.yml files?
I'm just starting to dip my toes in docker. Most of my stuff is kvm and physical.
Due to a desire to get off Ubuntu I have a goal to rebuild everything on Debian and/or containers and would like to document as I go.
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
(3 replies)
Hackmd.io for simple markdown docs.
I'm using anytype.io, it's been pretty neat so far.
I use bookstack. Simple selfhosted wiki.
+1 for bookstack. I also selfhost a kanban with the services basic info and it's related status (pilot/test, production and to be decommissioned). At the beginning I used Planka, but now switched to Nextcloud Deck.