Git Ignore... But for Dropbox...
Nope. This uses extended file attributes to flag files as ignored.
Running the command dropbox-ignore will look for a .dbignore file in the current directory and ignores any file that matches the pattern (using . as the root). The pattern is the same as for a git ignore file.
If you already have a .gitignore file in a directory, simply run dropbox-ignore -g to use it instead of a .dbignore file.
These are built via the action here
TODO: Create script to automate this
- Download the release for your OS and architecture
- Move the binary to a location in your
$PATH - Ensure it is executable
brew tap willfantom/dropbox-ignore
brew install dropbox-ignore
Dropbox Ignore has a key difference from gitignore. Adding a file to a gitignore will prevent git from staging future changes to the file however, the file state from the prior commit will be kept. Dropbox Ignore will simply flag the file as ignored. This will remove it from your dropbox if is already there! TL;DR only add files to the dropbox ignore file that you want no trace of in your cloud.
Dropbox does store deleted files for a time, thus a mistake here may be recoverable.
On MacOS: Yes... Otherwise No...