Hello,
how do I use the “ignore patterns” feature on a folder I don’t have write permissions on?
Since I can’t write the .stignore file, I don’t know how to do it.
acolomb
May 6, 2022, 8:50pm
2
Hi!
I’m pretty sure this is currently impossible. The .stfolder marker name can be configured, as the FAQ states, but the .stignore file is hard-coded.
Seems like a valid use-case though. So you could open a feature request on GitHub and with a little luck someone will implement a similar option for the ignore patterns file. One major problem is that if you can’t write an .stignore file, then you likely cannot write your patterns to another file in the folder either. So it will have to live outside the folder in question.
The feature request is already there
opened 01:33AM - 21 Jul 21 UTC
enhancement
### Include required information
#### what problem your new feature would solve…
Not relying on CoW for different ignores. There are a few send-only syncthing shares from the same directory.
#### how or why you think it is generally useful (i.e., not just for you)
edit: this is 'how it would be useful only for me' isn't it…
To share differing amounts of the same content to different peers/_client devices_. For example, the 2 data controllers have a normal syncthing share of the whole directory between them, and then another share for controller-side subscriptions¹.
¹ File and folder prefix² on what client syncs what. I went with `s-{2-letter-device-name}¤`, `s-x¤` (for exclude, even if included). One device has something like this:
```
// global
*.part
s-x¤*
s-x_*¤*
!s-g¤*
!s-g_*¤*
// for rodenode
!s*-rn¤*
!s*-rn-*¤*
!s*-rn_*¤*
*
```
Controllers have something like this:
```
// global
*.part
s-x¤*
s-x_*¤*
!s-g¤*
!s-g_*¤*
// for rodenode
!s*-rn¤*
!s*-rn-*¤*
!s*-rn_*¤*
// for thonknode
!s*-tn¤*
!s*-tn-*¤*
!s*-tn_*¤*
*
```
Individual files or whole directories of the multi-TiB shares may be synced with devices based on the device's storage capabilities. Around half of the files are only on controllers, yet ready to sync on need.
The share between controllers syncs all files, including the ones ignored by other shares. The controllers do not transfer data between other controllers using the share(s) other devices use. This allows multiple rw shares without major conflicts.
² Planning to switch to suffix, as devices I use this feature with are not Windows, and as such don't rely on file endings. The prefixes get in the way of sorting the files.
#### what alternatives or workarounds you considered
On the main 'server', docker is used, so one underlying directory can be expressed as 2 different directories to syncthing, where the second directory is using `/dir/.stignore2:/dir2/.stignore:rw`.
Yet on the secondary (soon to be equal) server/controller/pot, syncthing does not run in a container. Since it's a CoW file system, creating many directories of the same content, and scheduling `rsync` to keep up to date is possible. Yet, it's inefficient in terms of resource usage.
Related (on un-hardcoding the implementation): #6001
system
June 6, 2022, 3:02am
4
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
.