We are aware of the issue with the badge emails resending to everyone, we apologise for the inconvenience - learn more here.
Forum Discussion
Feedback on the new desktop app "ignore files" feature.
@Daphne that's great news! I look forward to trying it out.
But it would also be nice to have a configuration file, like ".dropboxignore", to list paths or patterns to exclude. The reason is that e...
Regards,
As an avid daily dropbox user and sr. programmer, rely on dropbox to synchronize my website folders across all my work stations. While I could use git pulls to synchronize my code folder files, I have thousands of other assets that I want to be synced alongside my codebase. Froma general workflow perspective, dropbox is meeting all my needs and is fast and efficient at accomplishing this task, at least until you get down to downloaded packages. For the developers in the room, you'll know what I'm talking about. "node_modules" or any other package system like "bower_components". When committing to git we use a .gitignore file to prevent these items from synching, I hope that dropbox will create a feature to support this. Now many people will say "they do, its called Selective Sync" however it doesn't work for 2 reasons. Firstly, I have to manually drill into each project folder to exclude the folder meaning that each new project I add to dropbox has to have a custom configuration. and Secondly, even when I do engage this feature, dropbox just starts making its own folders calling them:
- "node_modules conflict 1"
- "node_modules conflict 2"
- "node_modules conflict 3"
- etc...
l humbly suggest dropbox create some sort of .gitignore system so I can globally exclude generated files regardless of where they are nested inside my dropbox.
