You might see that the Dropbox Community team have been busy working on some major updates to the Community itself! So, here is some info on what’s changed, what’s staying the same and what you can expect from the Dropbox Community overall.
Forum Discussion
Feedback on the new desktop app "ignore files" feature.
@Daphne that's great news! I look forward to trying it out.
But it would also be nice to have a configuration file, like ".dropboxignore", to list paths or patterns to exclude. The reason is that extended attributes are tied to the actual file or folder, and will be gone if the file or folder is deleted and recreated.
The common use case for this is a software build folder that gets deleted and recreated on clean builds. Under xattr system, the "new" build folder would sync to Dropbox even if the "old" build folder had the necessary com.dropbox.ignored xattr.
How can one prevent dropbox from sync specific filetypes (across all folders) like temporary files from processes running in folders that are synched by dropbox (i.e. *.aux or *.log files from a latex build)?
The new selective synch feature can ignore individual files (https://help.dropbox.com/files-folders/restore-delete/ignored-files), but I do not see how to ignore file groups...
No, no they don't.
It is safe to say that the community is actively ignored. As a dev in a corporate enviroment, no amount of red tape can delay any development this long. The business clearly has no intrest in fixing this issue.At this junction I will fix it for them, for free. But alas. No.
But they are working on the next hair brained tie-in to the echo-system to increase their value offering... instead of fixing the stuff we actually need done.
The stupid powershell command to exclude a folder barely works:> Set-Content -Path 'your_local_path' -Stream com.dropbox.ignored -Value 1
It still goes into an absolute frenzy to index everything for some dark and dasterdly reason. Yet seems to hede the setting, and skip syncing.
Set-Content -Path 'C:\Users\...\Dropbox\...\node_modules' -Stream com.dropbox.ignored -Value 1
This really doesn't work for folders in PowerShell 7.1.4:Set-Content: Unable to clear content of 'C:\Users\...\Dropbox\...\node_modules' because it is a directory. Clear-Content is only supported on files.___
Update: It seems to be working in PowerShell 7.2.0-preview.9
- I came here hoping to see the .dropboxignore solution had been implemented but it seems Dropbox has placed a .ignore on the problem…
😞
