Selfhosted

37811 readers

680 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:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

Homelab Organization (lemm.ee)

submitted 5 days ago* (last edited 5 days ago) by Hellmo_Luciferrari@lemm.ee to c/selfhosted@lemmy.world

56 comments fedilink hide all child comments

Hi all!

So I want to get back into self hosting, but every time I have stopped is because I have lack of documentation to fix things that break. So I pose a question, how do you all go about keeping your setup documented? What programs do you use?

I have leaning towards open source software, so things like OneNote, or anything Microsoft are out of the question.

Edit: I didn't want to add another post and annoy people, but had another inquiry:

What ReverseProxy do you use? I plan to run a bunch of services from docker, and would like to be able to reserve an IP:Port to something like service.mylocaldomain.lan

I already have Unbound setup on my PiHole, so I have the ability to set DNS records internally.

Bonus points if whatever ReverseProxy setup can accomplish SSL cert automation.

you are viewing a single comment's thread
view the rest of the comments

[–] suswrkr@discuss.tchncs.de 9 points 5 days ago (1 children)

I run a k3s cluster for selfhosted apps and keep all the configuration and docs in a git repo. That way I have history of changes and can rollback if needed. In that repo I have a docs folder with markdown documents about common operations and runbooks.

There are other ways to do this, but I like keeping docs next to the code and config so I can update them all at the same time. Deployed several wikis in the past but always forget to update them when I change things.

[–] Hellmo_Luciferrari@lemm.ee 3 points 5 days ago (2 children)

I really should spend time familiarizing with maintaining a git repo. I'll likely find one I can self host.

[–] suswrkr@discuss.tchncs.de 6 points 5 days ago (1 children)

https://forgejo.org selfhosted has been good for me, FOSS fork of Gitea.

[–] Hellmo_Luciferrari@lemm.ee 1 points 5 days ago

Thank you for the suggestion. The fact that it's FOSS wins my vote. I have been trying to go all open source where possible.

[–] TCB13@lemmy.world 1 points 4 days ago (1 children)

If you want a git "server" quick and low maintenance then gitolite is most likely the best choice. https://gitolite.com/gitolite/index.html

It simply acts as a server that you can clone with any git client and the coolest part is that you use git commits to create repositories and manage users as well. Very very or no maintenance at all. I've been using it personally for years but also saw it being used at some large companies because it simply gets the job done and doesn't bother anyone.

[–] Hellmo_Luciferrari@lemm.ee 1 points 4 days ago

I will have to check out gitolite. Thank you!