4 ms·

I've been using mutagen for over 6 months now to sync over an M1 Linux VM. The only thing I miss is an option that would say "force everything from A" or "force

by ta988 4y ago

I've been using mutagen for over 6 months now to sync over an M1 Linux VM. The only thing I miss is an option that would say "force everything from A" or "force everything from B" I've had rare cases where there were conflicts that I only could resolve by pausing mutagen and running rsync. But I appreciate that mutagen warns you and just doesn't overwrite silently like syncthing can do sometimes.

ithkuil 4y ago
Mutagen allows to choose a replication mode: https://mutagen.io/documentation/synchronization https://mutagen.io/documentation/synchronization Do you want something different from the "one-way-replica" mode?
- ta988 4y ago
  Yes because I have generated files too that I can edit further, and need to send log files, screenshots etc to other people.
  - xenoscopic 4y ago
    One option I often recommend is setting up multiple synchronization sessions targeting different parts of a particular codebase with different synchronization configurations (kept mutually exclusive via ignore specifications). Quite often people want unidirectional replicas for a certain folder (e.g. a build directory) with more standard bidirectional synchronization for the rest of the code. It can be a little more complex to orchestrate, but you can use Mutagen's project functionality or a shell script to automate the setup a bit.
    - ta988 4y ago
      Yes I have that too, node modules are one way toward my host machine so my IDE can use them and a few things like that like logs
em-bee 4y ago
when does syncthing overwrite changes. that should not happen and would be a major bug
- ta988 4y ago
  When machines were not online at the same time or with unreliable connectivity. I've managed to never loose data because I have staggered backups so I could always revert to the in-between version.
- comfypotato 4y ago
  I’ve only ever casually browsed information about syncthing. Even I’ve stumbled across stories of people with a naive setup that, once fired up, started erasing all their files. I understand that this is probably an oversimplification, but I’ve read at least two separate stories that are along those lines. The comments for both stories were basically “yeah that sounds right because of the way you set it up”. It’s not a bug so much as how synchthing works. My understanding is that there is a circumstance where you sync an empty folder with a folder with your documents, and it decides to synch the empty folder such that it erases the documents. Without any kind of warning. Wild.
  - em-bee 4y ago
    maybe some people get confused thinking that unidirectional sync (send only) works like a backup? it is possible to use syncthing for backups, but that is actually one of the pain points. there is an option to specify to ignore deletes, but that option is hidden in advanced settings, and there is no quick way to check if it is turned on. every time i delete something that i want to keep on the backup side. (like pictures from my phone, where i am running out of space) i first go to the destination/backup server and double check that this option is turned on to make sure that i won't accidentally have the backup deleted too. it's also an issue that i can't see the remote settings from the client side. i have to connect to the remote server to check. there is also a problem with the way it resolves conflicts. if you have "ignore delete" set up, and then you delete files, syncthing will tell you that the two locations are out of sync. it offers a button to force a sync, but there is no preview explaining what that button will do. there is also no choice in how the out-of-sync status should be resolved (in which direction the sync should happen to get the two locations in sync). i have always been afraid to ever push that button, and there is no way to make it go away. i think this is an UX bug, because if i intentionally configure to ignore deletes, then deletes should not count as a difference. they should actually be ignored.

by ta988 4y ago

ithkuil 4y ago

Mutagen allows to choose a replication mode: https://mutagen.io/documentation/synchronization https://mutagen.io/documentation/synchronization Do you want something different from the "one-way-replica" mode?

ta988 4y ago
Yes because I have generated files too that I can edit further, and need to send log files, screenshots etc to other people.
- xenoscopic 4y ago
  One option I often recommend is setting up multiple synchronization sessions targeting different parts of a particular codebase with different synchronization configurations (kept mutually exclusive via ignore specifications). Quite often people want unidirectional replicas for a certain folder (e.g. a build directory) with more standard bidirectional synchronization for the rest of the code. It can be a little more complex to orchestrate, but you can use Mutagen's project functionality or a shell script to automate the setup a bit.
  - ta988 4y ago
    Yes I have that too, node modules are one way toward my host machine so my IDE can use them and a few things like that like logs

em-bee 4y ago

when does syncthing overwrite changes. that should not happen and would be a major bug

ta988 4y ago
When machines were not online at the same time or with unreliable connectivity. I've managed to never loose data because I have staggered backups so I could always revert to the in-between version.
comfypotato 4y ago
I’ve only ever casually browsed information about syncthing. Even I’ve stumbled across stories of people with a naive setup that, once fired up, started erasing all their files. I understand that this is probably an oversimplification, but I’ve read at least two separate stories that are along those lines. The comments for both stories were basically “yeah that sounds right because of the way you set it up”. It’s not a bug so much as how synchthing works. My understanding is that there is a circumstance where you sync an empty folder with a folder with your documents, and it decides to synch the empty folder such that it erases the documents. Without any kind of warning. Wild.
- em-bee 4y ago
  maybe some people get confused thinking that unidirectional sync (send only) works like a backup? it is possible to use syncthing for backups, but that is actually one of the pain points. there is an option to specify to ignore deletes, but that option is hidden in advanced settings, and there is no quick way to check if it is turned on. every time i delete something that i want to keep on the backup side. (like pictures from my phone, where i am running out of space) i first go to the destination/backup server and double check that this option is turned on to make sure that i won't accidentally have the backup deleted too. it's also an issue that i can't see the remote settings from the client side. i have to connect to the remote server to check. there is also a problem with the way it resolves conflicts. if you have "ignore delete" set up, and then you delete files, syncthing will tell you that the two locations are out of sync. it offers a button to force a sync, but there is no preview explaining what that button will do. there is also no choice in how the out-of-sync status should be resolved (in which direction the sync should happen to get the two locations in sync). i have always been afraid to ever push that button, and there is no way to make it go away. i think this is an UX bug, because if i intentionally configure to ignore deletes, then deletes should not count as a difference. they should actually be ignored.