What's the easiest way to duplicate all your Github repositories, with history, somewhere else?
Ideally, I'd like to have two synchronized repositories, for no single point of failure, organizational or otherwise.
GitHub was down again
71–80 of 125 posts
Re: GitHub was down again
#72Don’t host yourself, it’s impossible to meet the reliability of the professionals
I used to agree. Now I work with a locally hosted github. It is down all the time and sometimes it just deletes all of the work from the past day. I thought it wasn't possible to do much worse, but I was obviously wrong.
At work I'm managing a gitlab instance for 15k users and 5k projects. Uptime is 100% since 1 year except for few minutes of planned downtimes every month for the monthly upgrade.
To be honest I expected it to be a lot harder and run into troubles ... But I always find answers quickly in gitlab doc or forum
Re: GitHub was down again
#73What's the easiest way to duplicate all your Github repositories, with history, somewhere else? Ideally, I'd like to have two synchronized repositories, for no single point of failure, organizational or otherwise.
git remote set-url --add origin git@somewhere.else:my-project
Re: GitHub was down again
#74What's the easiest way to duplicate all your Github repositories, with history, somewhere else? Ideally, I'd like to have two synchronized repositories, for no single point of failure, organizational or otherwise.
You could probably use GitHub actions to push any commits and branches to GitLab or anywhere else.
Re: GitHub was down again
#75What's the easiest way to duplicate all your Github repositories, with history, somewhere else? Ideally, I'd like to have two synchronized repositories, for no single point of failure, organizational or otherwise.
git add remote NAME URL
git push NAME
Re: GitHub was down again
#76What's the easiest way to duplicate all your Github repositories, with history, somewhere else? Ideally, I'd like to have two synchronized repositories, for no single point of failure, organizational or otherwise.
Gitlab has a feature set for this that's automated but it may be rolled under a paid plan if you want it to be bidirectional.
Building this in git itself is not hard at all, and there's likely a script or plugin for gogs or gitea.
Re: GitHub was down again
#77What's the easiest way to duplicate all your Github repositories, with history, somewhere else? Ideally, I'd like to have two synchronized repositories, for no single point of failure, organizational or otherwise.
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-gi...
Re: GitHub was down again
#78https://gitea.io/en-us/ https://git.zx2c4.com/cgit/ https://about.gitlab.com/install/?version=ce
https://gogs.io/ as well
Re: GitHub was down again
#79Re: GitHub was down again
#80What's the easiest way to duplicate all your Github repositories, with history, somewhere else? Ideally, I'd like to have two synchronized repositories, for no single point of failure, organizational or otherwise.
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-gi...
I 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