Skip to content

Feat : Fix backup file naming for Windows 11 compatibility (#2955) - #2956

Merged
Siumauricio merged 5 commits into
Dokploy:canaryfrom
Harikrishnan1367709:Change-backup-file-naming-structure-#2955
Apr 3, 2026
Merged

Feat : Fix backup file naming for Windows 11 compatibility (#2955)#2956
Siumauricio merged 5 commits into
Dokploy:canaryfrom
Harikrishnan1367709:Change-backup-file-naming-structure-#2955

Conversation

@Harikrishnan1367709

Copy link
Copy Markdown
Contributor

Problem

Backup files with timestamps containing colons (:) were being truncated/renamed when downloaded on Windows 11, making them unidentifiable.

Solution

Updated backup file naming format from YYYY-MM-DDTHH:MM:SS.SSSZ to YYYY-MM-DD_HH-MM-SS_SSSZ by replacing:

  • T_ (date/time separator)
  • :- (time separators)
  • ._ (milliseconds separator)

Example

Before: 2024-01-15T14:30:45.123Z.tar
After: 2024-01-15_14-30-45_123Z.tar

@dosubot dosubot Bot added the size:M This PR changes 30-99 lines, ignoring generated files. label Apr 3, 2026
Siumauricio and others added 2 commits April 3, 2026 17:13
…stamp utility

- Replaced inline timestamp generation with the new getBackupTimestamp function across various backup modules (compose, libsql, mariadb, mongo, mysql, postgres, web-server, and volume-backups).
- Improved code readability and maintainability by centralizing timestamp formatting logic.
@Siumauricio
Siumauricio merged commit 2e8e2dc into Dokploy:canary Apr 3, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size:M This PR changes 30-99 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants