view the rest of the comments
Selfhosted
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.
-
No spam.
-
Posts are to be related to self-hosting.
-
Don't duplicate the full text of your blog or readme if you're providing a link.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
-
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.
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!
Edit: Was asking about the config targetting process for git (not how to use git) and was going to ask an AI to do some googling for me.
Please don't use AI for simple things like this.
The Odin Project has a tutorial on Git Basics and a guide on Setting Up Git. The instructions are roughly the same whether on Github, Codeberg, etc.
Once you have the repository, it's as simple as:
https://docs.codeberg.org/getting-started/first-repository/
Follow this, should suffice
That's what you just got shown: Shove the configgy bits into Git.
You will likely have to find the configs you want to save first.
I was hoping for a guide to capture said configs with a recommended subset. Not instructions for using git.
So no the guides don't help with that.
I'll just stick to my mkdocs repo.