sameersbn / sameersbn/docker-gitlab
README.md may be out-of-date
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 8.1k
- Forks
- 2.1k
- Avg merge
- 17h 47m
- Merged PRs (30d)
- 7
Description
I don't believe the README.md is reflective of the most recent changes shown in Gitlab's documentation.
I am not using docker-compose, but I have observed errors when attempting to restore using only the EPOCH. The command I am using was illustrated below with docker exec.
In GitLab 9.2 the timestamp format was changed; from EPOCH_YYYY_MM_DD to EPOCH_YYYY_MM_DD_GitLab version.
When running docker exec -it $CONTAINER /sbin/entrypoint.sh app:rake gitlab:backup:restore BACKUP=$BACKUP requires the $BACKUP variable to be defined in the v9.2+ format.
This appears to differ from the commands cited within README.md, in section #restoring-backups. The README.md presents BACKUP=1417624827 which appears to only identify the EPOCH. I haven't been able to restore backups using only the EPOCH for quite a few versions.
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
Read README.md's #restoring-backups section alongside the linked GitLab backup and restore documentation. Verify the BACKUP timestamp format and docker exec example, then update the README so its restore instructions match GitLab 9.2 and later.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, shell
- Domain
- devops, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100