Current State of Sync Operations

[emk-69]

Hi all,
Before trying this, I hope someone here can confirm whether or not either alternative will work.

Use Case: 2 Linux desktops (Ubuntu and/or Debian) both migrating from Keepass2 to KeepassXC using the "same" password file. Currently, Keepass2 runs 24x7 on both hosts. There is also one Android that periodically takes a copy of the file and uses it read-only. The common element is a Synology NAS. Both the desktops actually use a copy of the password file and do a periodic (nightly) sync to the master on the NAS (using a local mount to the NAS). Synology software sync's the master with each desktop's copy and the nightly sync done by a Keepass2 Trigger that merges the file content (retaining the newest passwords and propagating deletions).

Goal: Switch from Keepass2 to KeepassXC on both desktops, replicating the original setup with a backup copy and a sync step.

Alternative 1: It appears that KeepassXC currently does not hold the password file open while it is running and can tell that the file has been updated externally. So:

• What does Keepass XC do when it sees the file has been changed? If one desktop has changed the password of an entry and saved the file, and the NAS has sync'd the new content to the open file on the other desktop, will that other desktop immediately see the new password?
• If KeepassXC silently does the equivalent of a merge upon detecting a change to the file, then my use case will work by keeping the backups and master on the NAS. Synology software will keep the latest file content on each host's running file, with the master file retained on the NAS. The Synology can make periodic backups.

Alternative 2: If KeepassXC needs to be commanded to Merge to see a change made by the other host, then a script file can be written to periodically do a Merge using keepassxc-cli. But:

• Can keepassxc-cli be run while the KeepassXC GUI is still running and with the standard password file open?
• If not, can the script force the GUI to close the file and then re-open it? Without having to put the password file's password in the script file in plain text?

Is there anything else I should be considering?
Thank you all,
Eric

[droidmonkey]

Recommend just trying out your questions to see how it works for you. Use a dummy database to ensure no data loss.

FWIW, the default settings are to auto save on changes and auto merge when the underlying file changes.