3 ms·
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
by sangnoir 4y ago
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
- capableweb 4y ago> 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 git@github.com: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 https://news.ycombinator.com/item?id=34603174)
- sangnoir 4y agoThis 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).