Allowing to sync the .stignore file - any caveats?

Yes, that sounds very cool. It would definitely allow for more personalised configuration. My solution is really just a quick, brute-force workaround :grimacing:.

Awesome, then we’re at least two who would use it! The question still stands if there’s a wide enough use-case for it. However, I haven’t really developed in Go, so I wouldn’t know where/how to start :sweat_smile:

1 Like

You can already achieve that by using include directive.

That’s true, however the current implementation does not allow including a file when the folder is added to a device. Adding for example #include .globalstignore to the rules when initially adding a folder will just throw an error, as the file doesn’t exist locally yet, which makes sense.

However I think it would be much better if Syncthing instead would pull the file(s) specified in the include(s) (if they exist in the cluster), apply those rules, and then begin pulling all other files.

The error thrown is this one

2020-08-02 19:13:19 Error on folder "Test" (94clu-ucu8j): loading ignores: failed to load include file .globalstignore: open \\?\[folder path]\.globalstignore: Det gÄr inte att hitta filen.

One solution could be a flag for optional includes (missing is not an error) combined with default ignore patterns (we want those anyhow).

Chicken-and-egg problem remains, but that’s the case with any synced-ignores setup