Performing Hotbackups of Gogs

This question is related to this question which targets only the gogs-repositories component of gogs / git:

Hotback of Git Server Using RSync?

  • Git as a backup tool: how to keep only latest N git commits both in local and remote?
  • Daily and weekly backup strategies
  • Git and Dropbox - local repo
  • Moving a Subversion repository to another server
  • Add/commit to bare repo from a non-git folder
  • Git as deployment, development and backup
  • Gogs also performs ‘health checks’ on the git repositories. What do these health checks do? Could they mutate the state of the repositories? If so could that cause corruption is the repositories are backed up using RSync?


  • git commit -a did not work
  • Git merge -s theirs: Simply?
  • How to rebase commits from another repository with a different history?
  • How to insert removed commits before my commits, and revert those removed commits?
  • When to use the '--no-ff' merge option in Git
  • How to view all pulls from bare repository?
  • One Solution collect form web for “Performing Hotbackups of Gogs”

    Ultimately I wanted to be able to perform efficient Cron based nightly backups while minimizing the chance of data corruption and being able to move the backup of site with encryption. I also needed a time machine capability in the event that for some reason something something did get corrupted (Even though going back to a previous commit is an option as well). Turns out duplicity has all of that built in and is a perfect fit:

    So that’s what I’m rolling with. I’m also planning to switch off the health checks and perform them outside of gogs on a separate CRON job, but I’m still researching the recipe for that. If anyone has tips please comment.

    Git Baby is a git and github fan, let's start git clone.