Totally second the Git style of ignoring files from sync. Like a .gitignore, support a .boxignore (or whatever) on the sync'd directory. Bonus if it could use an apache .htaccess inheritance, so per subdirectory you could add/remove paths to ignore.
It's virtually impossible to use box to sync programming projects between systems, even just to maintain a backup. Source files, images, etc. should sync, but compiled binary files, node_modules/, vendor/, .env, etc. files and directories have to be excluded.
Since DropBox/Google Drive also don't have this functionality, adding such a feature would also be a differentiator making Box a better solution for programmers and advanced users.
Anonymous
Totally second the Git style of ignoring files from sync. Like a .gitignore, support a .boxignore (or whatever) on the sync'd directory. Bonus if it could use an apache .htaccess inheritance, so per subdirectory you could add/remove paths to ignore.
It's virtually impossible to use box to sync programming projects between systems, even just to maintain a backup. Source files, images, etc. should sync, but compiled binary files, node_modules/, vendor/, .env, etc. files and directories have to be excluded.
Since DropBox/Google Drive also don't have this functionality, adding such a feature would also be a differentiator making Box a better solution for programmers and advanced users.