docker-gitlab
docker-gitlab copied to clipboard
README.md may be out-of-date
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.
Why did you close this ?
Someone's idea of a practical joke ._. Trying to find a copy of what I had written, to repost and reopen.
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.
Feel free to make an Pull Request for this 😏 .
Thanks! Phew! Yeah, I was considering doing a PR once I determined if this was accurate. Need to DL docker-compose, and it's restricted on the machine I'm currently working from.
Note for myself (or anyone interested), This also ties into: assets/runtime/functions#L1643 and docs/s3_compatible_storage#restoring-backups
Trying to go back and clean up issues that are open or pending. I've had to relocate and access to the work that I had been performing is currently inaccessible.
Given my appreciation of this library, I'll try and catch up on what I had been doing and see if I can clean up the documentation over the remainder of this week.
This issue has been automatically marked as stale because it has not had any activity for the last 60 days. It will be closed if no further activity occurs during the next 7 days. Thank you for your contributions.
I did note the same , and I believe thre are other outdated topics. We may open issue by topic