Steve Grunwell

Good point, this is something that should be better documented. You can find all of the existing exclusions with the following ([props to Heissenberger Laboratory](https://www.heissenberger.at/en/blog/macos-exclude-node_modules-folder-from-time-machine/)): ```sh $ find ~ -xattrname...

> What i can suggest is to make it conditional to exclude `DerivedData` unless an Xcode project file exists in the directory? Which would be anything like `*.xcodeproj`. I think...

From the docs, it looks like this is `Package.swift` and `Packages/`, correct?

First, thanks for bringing up this excellent point. When building Asimov initially, I was so concerned with **historical** dev dependencies that I wasn't even thinking about those that would be...

Asimov is always down for additional Time Machine exclusions! Right now, [the list is defined as `$FILEPATHS`](https://github.com/stevegrunwell/asimov/blob/develop/asimov#L19): ```sh readonly FILEPATHS=( "vendor ../composer.json" "node_modules ../package.json" ".vagrant ../Vagrantfile" "bower_components ../bower.json" ) ```...

That's a very good question, and definitely worth looking into. Anyone have more experience with `.plist` files and care to weigh in?

As @codexp mentioned above, Asimov doesn't remove those directories from existing backups, it only prevents them from being added to or updated in Time Machine. This does raise a gap...

This seems perfectly sensible, thanks for the suggestion!

It could be argued that this goes well beyond the scope of keeping development dependencies out of Time Machine, but...damn, this is a good idea. Also, music could pretty easily...

Keeping this open as a reminder to make the docs clearer 😄 Thanks, @saltcod!