Tell HN: GitHub will delete your private repo if you lose access to the original

Re:Tell HN: GitHub will delete your private repo if you lose... by sangnoir on Tuesday January 31, 2023 @06:54PM (#34604158)

Gitea has a cron task that pulls-in changes on an ongoing basis.

If a snapshot suffices, a once off "git push" or "git clone" works (but that's not too far off from downloading a tar ball, is it?). If you want to have a up-to-date local copies of multiple repos, a SQLite-backed Gitea instance is the simplest solution.

An added bonus to using Gitea is flexibility in mirroring LFS objects, which can be sent to S3 or minio

[ Parent | on HN ]

Re:Tell HN: GitHub will delete your private repo if you lose... by capableweb on Tuesday January 31, 2023 @07:14PM (#34604343)

> a SQLite-backed Gitea instance is the simplest solution

Agree to disagree :)

This seems like the simplest solution:

    git remote set-url --add --push origin [email protected]:my-user/my-repo.git
    git remote set-url --add --push origin /backups/repos/my-user/my-repo.git

Now when you push to origin, it pushes to your local backup as well, everything up to date, no external sosftware at all :)

Thanks dabber for sharing this trick (https://news.ycombinator.com/item?id=34603174)

[ Parent | on HN ]

Re:Tell HN: GitHub will delete your private repo if you lose... by sangnoir on Tuesday January 31, 2023 @07:41PM (#34604614)

This does not include the cron jobs to pull in changes others make daily/weekly/every N hours. I mentioned that Gitea is superior under very specific conditions (where one wants to have latest version available locally).

[ Parent | on HN ]