If i understand you, you are saying that a gittea is a "remote server" and isn't necessary because it implies sharing with others? And by extention I don't need gittea per se but rather just clone the software to my computer.
And that the gitea is for me to be able to share with others in the future easily?
yes. That's exactly right. Or... you can use github or codeberg or a myriad of other remote servers in the future if you want to share but don't want to host your own code server.
All you need is git. it's just a program.
My main objective is to hold my own copy of the most integral foss I use. I feel a need to distribute the code base beyond centralized github servers.
Then you just use git to clone from whatever remote server is hosting it. Usually github.
`git clone https://github.com/bitcoin/bitcoin`
Will clone the official bitcoin repo from github onto your local system.
This is the source code, so to run bitcoin, you would have to compile the executables using the source code. That requires dependencies but that's how you use git to clone software you want.
And using a gitea would allow that software to be shared later?
If you ran git tea, you can
`git remote add origin yourgitteaserver.com`
Then push it to your remote with
`git push`
This will "push" the code in your local directory to your remote server. (Which in this case would also be local) But others can access your code with
`git clone yourgitteaserver.com/user/project.git`
And they can clone your code onto their local directory.
The takeaway is git is just a version control software.
A git remote server is a server you can use to host your code for you or others. Remote servers can also do things like GitHub actions and perform tasks in a container on push or commit or whatever other rules you want to make.
