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
.dropbox-ignore to prevent folders being uploaded to DropBox like git's .gitignore
Just like we have .gitignore for preventing files / folders to be uploaded to github, it would be nice to have the same for DropBox.
I have a workspace folder with tons of node_modules folders.
I...
Got the answer here : https://help.dropbox.com/files-folders/restore-delete/ignored-files
This might be useful for others on Windows and Powershell with the git command line tool installed.
The script finds all .gitignore files in current folder and subfolder and sets the ignored files and folders to not upload to Dropbox.
Get-ChildItem -Recurse | `
Where-Object { $_.Name -eq '.gitignore' } | `
ForEach-Object { `
Write-Host $_.DirectoryName; `
Push-Location $_.DirectoryName; `
git status --ignored --short | `
Where-Object { $_.StartsWith('!! ') } | `
ForEach-Object { `
$ignore = $_.Split(' ')[1].Trim('/'); `
Write-Host $ignore; `
Set-Content -Path $ignore -Stream com.dropbox.ignored -Value 1 `
}; `
Pop-Location }You can paste this into say `dropbox-sync-ignore.ps1` and store in your PATH and run it whenever you start or update a project in git.
DropBox should come up with an update that provides this out of the box. Right now running this
xattr -w com.dropbox.ignored 1 /Users/yourname/Dropbox/workspace/react-project/node_modules
for every node project manually is a pain.
Try this one:
`xattr -w com.dropbox.ignored 1 /Users/yourname/Dropbox/**/node_modules`
It should mark recursively all node module folders in your Dropbox.I got it working like denysp said, but I needed to add the -r param, so:
`xattr -rw com.dropbox.ignored 1 /Users/yourname/Dropbox/**/node_modules`
Update: Actually, both commands seem to work, but you need to run it again every time a new node_modules dir is created (eg every time you npm install a new repo), it won't ignore new ones automatically 😞
At least that's slightly better than running a new custom command for every repo.
