| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
| |
As far as I know, these are out of date, unmaintained and nobody is
using them. It was definitely a useful learning process to integrate
Gitlab into Baserock, but I think this is now just taking up space in
definitions.git needlessly.
Change-Id: Ifdd9c0a3dd889382bc5e6825c2df4f3afbd89f3c
|
| |
|
|
|
|
|
|
|
| |
- Scripts written by Lars Wirzenius.
- Reviewed by Michael Drake.
These scripts are to be copied to the system on which the
backups are made. They are stored here to keep the related
logic in one source location.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
The Gitlab Rake script for backing up doesn't backup the database
that Gitlab CI uses, and additonally it does a git bundle for each
git repository. Our GitLab instance has hundreds of git repositories,
making the bundling be a very expensive things.
Instead, we use the Postgres tool to dump all databases to a file,
and arrange to backup the dump files, the git repositories, and all
other relevant files directly.
|
| | |
|
| | |
|
| |
|
|
|
|
| |
This adds a systemd timer unit to back up a GitLab instance every
four hours. The backup is placed as /home/git/gitlab-backup.tar and
it is expected Something Else retrieves that.
|
| |
|
