recommended way to sync a tomb

[chri2]

Which is the recommended way to sync a tomb? My thoughts are the following so far:

• syncing an open tomb probably is not helpful, because it conflicts with processes writing to the tomb at the same time leaving the tombs filesystem in an unpredictable state
  • best approach seems to sync closed tombs only
• since the syncing software doesn't know anything about the tombs content it's hard to decide which version of two tomb files is more recent - except for the closing time which should be reflected by mtime(?)
  • keep a long history of versions of tomb files to make it easy to manually merge any entry that has gotten lost - if that ever happens
  • I'm the only user of my pass-tomb using it on a handful of devices.
  • Conflicts should be rare, because good practice would be to leave the tomb not open on a device I'm not using anymore.
• how should I find the right moment to sync?
  • Is there a hook for open and close on a pass-tomb I didn't stumble over?
  • I'm using a gpg key from a nitrokey. This gives me udev-events when inserting and removing the nitrokey: could sync on removal (outgoing) and on connect (incoming)

Side note: should think about how important it is to me to protect the file structure of my pass content by a tomb. Is it sufficient for me to have it protected "on the road" carrying a tomb file, but push it to a self-hosted git repository? In the light of the thoughts above this seems to be a compromise.

Any thoughts, help, further information on this would be very welcome 😏 !

[aikooo7]

Hello @chri2 I know this is a year latter 💀 but my approach is using git on the closed tomb so you know when changes and have a helpfull (or not) commit message.

[kqvanity]

Will this ever be responded to?