Your workflow is unique 👨💻 - tell us how you use Dropbox here.
Forum Discussion
vladgasan
Dropbox Product Manager
Dropbox Product ManagerCut the Clutter: Ignore Files Feature is now live
Update: This feature is now live and available to all individual plan customers! Thank you to all our testers, and share your feedback with the team, we're still eager to hear from you!
For ye...
Dell_Dropbox So I enabled the early access feature, went to sync options, and clicked Modify the rules, which created the rules.dropboxignore file. I did this on both machines and added two rules as a test: one for a file and one for a folder. Both are regularly deleted and recreated whenever the IDE performs a complete build.
/Projects/**/Cargo.lock
/Projects/**/target/
I have a directory structure that looks something like this:
/<folders>/<files>
/Projects/<projectname>/src/*
/Projects/<projectname>/target/*
/Projects/<projectname>/Cargo.lock
/Projects/<projectname>/Cargo.toml
/Projects/<projectname>/<other files>
/Projects/<groupname>/<projectname>/src/*
/Projects/<groupname>/<projectname>/target/*
/Projects/<groupname>/<projectname>/Cargo.lock
/Projects/<groupname>/<projectname>/Cargo.toml
/Projects/<groupname>/<projectname>/<other files>
Based on the rules above, I would assume the following would be ignored; however, they appear to be still synced every time I build, which creates 10s of thousands of files.
/Projects/<projectname>/target/*
/Projects/<projectname>/Cargo.lock
/Projects/<groupname>/<projectname>/target/*
/Projects/<groupname>/<projectname>/Cargo.lock
Dell_Dropbox
Community Manager
Community ManagerPinging vladgasan for this one, maybe we can get a little help
