Jim McBride e71e6bc3d7 Fix backup timestamp display to use UTC timezone ... The list_backups function was creating timezone-naive datetime objects, which caused the frontend to incorrectly interpret timestamps. Now uses datetime.UTC when creating timestamps from file modification time (consistent with other usage in this file on lines 186, 216), so the ISO string includes timezone info (+00:00). This allows the browser to properly convert UTC timestamps to the user's local timezone for display. Before: Backend sends "2025-12-09T14:12:44" (ambiguous timezone) After: Backend sends "2025-12-09T14:12:44+00:00" (explicit UTC) The frontend's toLocaleString() will now correctly convert to local time.		2025-12-09 08:16:04 -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	Fix backup timestamp display to use UTC timezone	2025-12-09 08:16:04 -06:00
tasks.py	Feature: Automated configuration backups with scheduling	2025-11-26 21:11:13 -06:00
tests.py	Update backup feature based on PR feedback	2025-12-02 19:33:27 -06:00