Skip to content

Add CLI flag to configure checkpoint file location#47

Merged
phrp720 merged 3 commits intophrp720:masterfrom
Deletus1:Add-New-Flag-for-Checkpoint-File
Feb 11, 2026
Merged

Add CLI flag to configure checkpoint file location#47
phrp720 merged 3 commits intophrp720:masterfrom
Deletus1:Add-New-Flag-for-Checkpoint-File

Conversation

@Deletus1
Copy link
Contributor

@Deletus1 Deletus1 commented Feb 9, 2026

The sync agent currently always creates its checkpoint file (checkpoint.json) in the current working directory.
This makes it difficult to:

  • Keep the development environment clean (checkpoint.json is created in the source directory during builds)
  • Align with custom filesystem layouts used in real deployments (e.g. production Electron apps)

In a project I was working on, I needed to control where the checkpoint file is stored.

Solution

This PR introduces a configurable checkpoint file location that can be set via a CLI flag.

Changes

  • Added a new checkpoint setting to configuration (settings.Settings.CheckpointFile)
  • Added a CLI flag to specify a custom checkpoint file path

Usage

aw-sync-agent -checkpoint=/path/to/checkpoint.json

Notes

  • Default behavior is unchanged: checkpoint.json is created in the current working directory when the new CLI flag is not used.

@phrp720 phrp720 merged commit 9fdd5fe into phrp720:master Feb 11, 2026
2 checks passed
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.

2 participants