Live data from Hacker News

Dropbox ignore file or folder in beta

help.dropbox.com

141–143 of 143 posts

Re: Dropbox ignore file or folder in beta

#141
post #65

The dropbox cli already lets you ignore folders. I've have had the following script for many years to ignore node_modules: exclude_folders=$(find . -type d -name "node_modules" | grep -v "node_modules/") echo "Excluding $exclude_folders" dropbox exclude add $exclude_folders dropbox exclude list The feature I want is pattern-based ignore in a .dropboxignore file.

I work on a major dropbox competitor. We have the ability to do regex-based ignores, but it's deliberately hidden. (And not part of any regression suite.) As we've optimized the product, regexes would cause a huge performance problem.

Why? Part of our optimization includes representing paths in an optimized data structure. In order to process the regex, each path would need to be converted back to its full string, which is computationally "expensive" when working with 20,000 or more files and folders.

Re: Dropbox ignore file or folder in beta

#142
post #109

Earlier quoted context omitted.

> If you look at something like Bazel, all the build artifacts end up in ~/.cache (or similar). That is a terrible design, as it makes parallel builds error prone.

Output directories are unique by the user and source project workspace directory. Output artifacts don't clobber, even though they are all in ~/.cache.

Other reasons to avoid the home directory:

1. It might be NFS mounted.

2. Space might be an issue and more difficult to plan for if build outputs are going there.

Re: Dropbox ignore file or folder in beta

#143
post #142

Earlier quoted context omitted.

Output directories are unique by the user and source project workspace directory. Output artifacts don't clobber, even though they are all in ~/.cache.

Other reasons to avoid the home directory: 1. It might be NFS mounted. 2. Space might be an issue and more difficult to plan for if build outputs are going there.

The location is not hard-coded and can be configured with the --output_base flag.
Post reply on HN