You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please use the 👍 reaction to show that you are interested into the same feature.
Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
Subscribe to receive notifications on status change and new comments.
Feature request
Which Nextcloud Version are you currently using: Latest / Irrelevant / 3.14.x
Describe the solution you'd like
It'd be nice if you could specify a particular parent directory name for ignoring files. For example, say I want to ignore the file OR directory named bar, but only when it is inside of foo. I could put either of the following entries for the desired use case:
foo/bar foo/bar/
If these entries respected the parent directory name, then any other folders not named foo would allow for bar to continue to be synced. This adds a layer of functionality to the pattern matching so that a very particular use case can be accomplished, and prevent the unnecessary ignoring of syncing in other places.
Describe alternatives you've considered
The only alternative which seems to exist is blocking the entire bar/ directory regardless of the parent foo/'s presence or not. This will often be okay, but in particular circumstances it may not be desirable. For example, when building Rust applications there are many files created in target/debug/ and target/release/. Nextcloud struggles with syncing a lot of tiny files, and there's really nothing important in these directories which requires syncing anyways. If many Rust project folders are present within a Nextcloud directory, it can be desirable to specifically block target/debug/ and target/release/ while not impacting other target folders for other build projects. Unfortunately, the only existing solution seems to be to block all target/ directories as of present.
I looked for duplicates, but I didn't see any. Apologies if I missed one.
The text was updated successfully, but these errors were encountered:
How to use GitHub
Feature request
Which Nextcloud Version are you currently using: Latest / Irrelevant / 3.14.x
Describe the solution you'd like
It'd be nice if you could specify a particular parent directory name for ignoring files. For example, say I want to ignore the file OR directory named
bar
, but only when it is inside offoo
. I could put either of the following entries for the desired use case:foo/bar
foo/bar/
If these entries respected the parent directory name, then any other folders not named foo would allow for bar to continue to be synced. This adds a layer of functionality to the pattern matching so that a very particular use case can be accomplished, and prevent the unnecessary ignoring of syncing in other places.
Describe alternatives you've considered
The only alternative which seems to exist is blocking the entire
bar/
directory regardless of the parentfoo/
's presence or not. This will often be okay, but in particular circumstances it may not be desirable. For example, when building Rust applications there are many files created intarget/debug/
andtarget/release/
. Nextcloud struggles with syncing a lot of tiny files, and there's really nothing important in these directories which requires syncing anyways. If many Rust project folders are present within a Nextcloud directory, it can be desirable to specifically blocktarget/debug/
andtarget/release/
while not impacting othertarget
folders for other build projects. Unfortunately, the only existing solution seems to be to block alltarget/
directories as of present.I looked for duplicates, but I didn't see any. Apologies if I missed one.
The text was updated successfully, but these errors were encountered: