sameersbn / sameersbn/docker-gitlab
Daily backup with cron
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 8.1k
- Forks
- 2.1k
- Avg merge
- 17h 47m
- Merged PRs (30d)
- 7
Description
I've recently set up the environnement var GITLAB_BACKUP_DIR.
Now each time I re-start my docker image, there is a new line in the git user crontab. And it's always the same.
root@synology_gitlab:/home/git/gitlab# crontab -l -u git
00 10 * * * /bin/bash -l -c 'cd /home/git/gitlab && bundle exec rake gitlab:backup:create SKIP
= RAILS_ENV=production'
00 10 * * * /bin/bash -l -c 'cd /home/git/gitlab && bundle exec rake gitlab:backup:create SKIP
= RAILS_ENV=production'
So the backup never start...
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting the Docker image startup path that configures the git user's crontab when GITLAB_BACKUP_DIR is set. Reproduce a restart and compare crontab -l -u git before and after; the work is done when the backup entry is added only once and the scheduled backup starts normally.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, shell
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100