4 ms·
Run git on a personal server[1]? It's not as complicated as you might think. Probably much more usable to setup gitlab. Then set up the alternative remote on y
by monokh 6y ago
Run git on a personal server[1]? It's not as complicated as you might think.
Probably much more usable to setup gitlab.
Then set up the alternative remote on your repos.
[1]https://www.linux.com/training-tutorials/how-run-your-own-git-server/ https://www.linux.com/training-tutorials/how-run-your-own-gi...
- rovr138 6y agoI posted this on another thread. If you only want the commits, something like this works, ssh user@git.example.com mkdir project-1.git cd project-1.git git init —-bare exit git remote add alternate user@git.example.com:project-1.git All you need is SSH
- kenniskrag 6y agoI use it also that way. Gitlab does the same if you use ssh. They provide hooks on init so that gitlab knows if something happens.
- judge2020 6y agoAll you need to get all commits and all tags/branches: git clone --mirror https://github.com/you/repo Push those to another server: git remote add new https://gitlab.com/you/repo git push --mirror new
- johannes1234321 6y agoThat's fine for your code repository. However git has more: - Bug tickets - PR - Wiki - many projects use their githubpages as primary homepage - newly GitHub actions And then: Often collaborators are only known and identified by their GitHub handle. Running an own server requires some mechanism to identify them again and creating a way to handle their access credentials (ssh key etc.) Moving a mildly successful project isn't easy. Good if more people plan for that eventuality, even if they stay on GH for the time being.