sameersbn / sameersbn/docker-gitlab
[11.0.1] Automated backup schedule isn't being updated after the environment variables change
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 8.1k
- Forks
- 2.1k
- Avg merge
- 17h 47m
- Merged PRs (30d)
- 7
Description
I had automated backups scheduled daily at 04:00 for a while. Last week I changed the schedule to a weekly backup at 01:00, but somehow it's still backing up daily on it's previous schedule.
Docker environment variable setup:
Files in the backups/ directory:
Are there any other settings or caches I have to change or delete? I'm running it on a Synology with the Docker package. I also have AWS_BACKUPS enabled if that makes any difference.
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 tracing how the Docker environment variables control the automated backup schedule and how the backups/ directory reflects that schedule. Check whether AWS_BACKUPS changes this behavior; done means changing from daily at 04:00 to weekly at 01:00 updates the active schedule without requiring unexplained cache or file deletion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, docker
- Domain
- cloud, devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100