Jim McBride 8388152d79 Use system timezone for backup filenames ... Updated create_backup to use the system's configured timezone for backup filenames instead of always using UTC. This makes filenames more intuitive and matches users' local time expectations. Changes: - Import pytz and CoreSettings - Get system timezone from CoreSettings.get_system_time_zone() - Convert current UTC time to system timezone for filename timestamp - Fallback to UTC if timezone conversion fails - Internal metadata timestamps remain UTC for consistency Example: - System timezone: America/New_York (EST) - Created at 3:00 PM EST - Old filename: dispatcharr-backup-2025.12.09.20.00.00.zip (UTC time) - New filename: dispatcharr-backup-2025.12.09.15.00.00.zip (local time) This aligns with the timezone-aware scheduling already implemented.		2025-12-09 09:06:22 -06:00
..
migrations	Feature: Automated configuration backups with scheduling	2025-11-26 21:11:13 -06:00
__init__.py	Feature: Automated configuration backups with scheduling	2025-11-26 21:11:13 -06:00
api_urls.py	Feature: Automated configuration backups with scheduling	2025-11-26 21:11:13 -06:00
api_views.py	Feature: Automated configuration backups with scheduling	2025-11-26 21:11:13 -06:00
apps.py	Feature: Automated configuration backups with scheduling	2025-11-26 21:11:13 -06:00
models.py	Feature: Automated configuration backups with scheduling	2025-11-26 21:11:13 -06:00
scheduler.py	Add custom cron expression support for backup scheduling	2025-12-09 07:55:47 -06:00
services.py	Use system timezone for backup filenames	2025-12-09 09:06:22 -06:00
tasks.py	Feature: Automated configuration backups with scheduling	2025-11-26 21:11:13 -06:00
tests.py	Add tests for cron expression functionality	2025-12-09 08:54:23 -06:00