Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/nknapp/gitolite-backup
A backup system for gitolite (this project is discontinued by me)
https://github.com/nknapp/gitolite-backup
Last synced: 20 days ago
JSON representation
A backup system for gitolite (this project is discontinued by me)
- Host: GitHub
- URL: https://github.com/nknapp/gitolite-backup
- Owner: nknapp
- Created: 2012-02-09T21:27:12.000Z (almost 13 years ago)
- Default Branch: master
- Last Pushed: 2012-02-09T21:27:51.000Z (almost 13 years ago)
- Last Synced: 2024-10-06T03:41:28.685Z (about 1 month ago)
- Language: Shell
- Homepage:
- Size: 89.8 KB
- Stars: 4
- Watchers: 4
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
Gitolite Backup
===============This project is intended to be a backup script for the gitolite hosting system.
At the moment, there is an "install.sh" script that can be used to setup the backup in the same location as the cloned repository
The "backup.sh" script builds a mirror of the whole gitolite home-directory without the repositories using "rsync". It then uses a "backup" user to mirror all repositories that this user can read. You can configure, which repositories should be backed up by setting appropriate read permissions for this user.
Using "git --mirror" to copy the repositories should also avoid inconsistencies when the backup is running during a push.
The idea is, that the whole thing is mirrorerd somewhere, where a real backup tool can read it.
**I give no warranty that using this script won't destroy your installation. I do not guarantee for neither script**
TODO
----* Restore process for single repositories
* More intelligent backup process (every repository already has the whole history, so we do not need to keep multiple instances of the backup, only the refs are needed in multiple instances).
* Copy the result somewhere safe. This is not done yet.Everything is still work in progress.