Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow specifying which folders should be checked by the syncthing sync check #246

Open
surskitt opened this issue Dec 5, 2024 · 2 comments
Assignees
Labels
investigating Looking into the reason for the issue and or a solution internally

Comments

@surskitt
Copy link

surskitt commented Dec 5, 2024

I am currently sharing two folders with my miyoo using syncthing. One containing my saves and a much larger one for the roms.

The syncthing sync check is often held up waiting on this large roms folder to finish scanning. Since syncthing is stopped while a game is running a new scan will happen before and after playing a game which ends up causing a wait on both startup and shutdown.

The saves folder is the one I would want to be in sync before shutting down the system or starting up a new game. It is small and the syncing and scanning does not take too long. It is not as important to keep the roms folder up to date so it could be ignored by the sync check.

@BaseInfinity
Copy link
Collaborator

BaseInfinity commented Dec 5, 2024

Hey there!

So it looks like a quick workaround you can do is visit your Syncthing GUI on your A30 and Pause the Roms directory for syncing.

The Syncthing Sync Check will now ignore that directory when doing a Sync Check. You can always Resume it when you enable new Roms.

We are currently discussing a long term solution here and trying to be thoughtful about use cases

Screenshot 2024-12-05 at 10 52 33 AM

@surskitt
Copy link
Author

surskitt commented Dec 6, 2024

I've already done exactly that! Wasn't completely sure it was doing what I wanted or needed, but it's good to have a confirmation.

@XanXic XanXic added the investigating Looking into the reason for the issue and or a solution internally label Dec 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
investigating Looking into the reason for the issue and or a solution internally
Projects
None yet
Development

No branches or pull requests

3 participants