Add timezone support for backup scheduling #85
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
This PR adds robust timezone support for scheduled backups.
Features
TZ
environment variable to control the timezone used for scheduled backups.TZ
is set, all scheduled backups are interpreted in the specified timezone. If not set, the system default timezone is used.Implementation
pytz
to handle timezone conversion in the backup process.TZ
.test_backup_timezone
) to verify that the backup logic correctly applies the timezone from theTZ
environment variable.Documentation
TZ
environment variable in your environment or docker-compose.yml.Testing
Use Case
This addresses the use case where users need to run scheduled backups in specific timezones, ensuring correct backup timing regardless of the system locale.
Closes #77