Skip to content

Preserve config files during save and retain unique backups - #230

Merged
LuisPalacios merged 1 commit into
mainfrom
fix/181-atomic-config-save
Nov 14, 2026
Merged

LuisPalacios merged 1 commit into
mainfrom
fix/181-atomic-config-save

Conversation

@LuisPalacios

Copy link
Copy Markdown
Owner

Closes #181

What changed

  • Stage, sync and close config files before replacing the live path, preserving permissions on both the config and its backups.
  • Publish complete backups without overwriting existing names; order and prune same-second snapshots consistently in storage and GUI recovery.
  • Document best-effort backups on filesystems without hard links, Windows rename limits and directory durability limits in English and Spanish.

Test plan

  • Injected I/O failures, concurrent backup publication, same-second ordering/exhaustion, permission preservation and GUI recovery tests.
  • Rebased onto Write credentials atomically and audit permissions #226 while preserving its startup/audit changes; focused and race tests, vet, full health, Wails build and version smoke.
  • Interactive recovery smoke and native Windows execution.

Interactive smoke testing remains required before merge.

Stage and sync config replacements before renaming, publish completed backup snapshots without overwriting existing names, and share chronological backup listing with recovery.

Closes #181
@LuisPalacios
LuisPalacios force-pushed the fix/181-atomic-config-save branch from 3f09686 to 23480d3 Compare November 14, 2026 09:59
@LuisPalacios
LuisPalacios merged commit e40d004 into main Nov 14, 2026
3 checks passed
@LuisPalacios
LuisPalacios deleted the fix/181-atomic-config-save branch November 14, 2026 10:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Phase 3] Atomic config save and unique backup names

1 participant