The most requested feature, to allow a file or folder to be ignored by Dropbox sync without using selective sync is finally in beta. The community requested a .dropboxignore file but they chose another solution which I’m sure is reasonable for making the feature more user friendly to non-devs. This will be immensely helpful for node_modules or build target directories.
> This will be immensely helpful for node_modules or build target directories. Why would anyone put a node project in Dropbox to begin with?
Dropbox ignore file or folder in beta
11–20 of 143 posts
Re: Dropbox ignore file or folder in beta
#12note: i'm a co-founder
Re: Dropbox ignore file or folder in beta
#13Re: Dropbox ignore file or folder in beta
#14Earlier quoted context omitted.
I can imagine a world where a arbitrary directory is filled with gitignore, dropboxignore, googledriveignore, backblazeignore, s3ignore, rsynciginore, dotignore, ipfsignore . . . Goddamn, stop the world I want to get off
That's probably a clue something needs to be done at the OS level regarding FS integration with cloud syncing systems and permissions.
On linux you can create an user group named "cloud", and allow dropbox to only sync files that belong to that group.
Re: Dropbox ignore file or folder in beta
#15Earlier quoted context omitted.
That's probably a clue something needs to be done at the OS level regarding FS integration with cloud syncing systems and permissions.
All major OS already have a permission' system. It's on dropbox & co to honor them. On linux you can create an user group named "cloud", and allow dropbox to only sync files that belong to that group.
What i envisionned was more like a "control center" app of all the outgoing (and incoming) pipes from your FS to syncing systems, with both last syncing time, configuration, etc. A little bit like what's already happening for mail and calendar integration into iOS applications, only for files and on the desktop.
Re: Dropbox ignore file or folder in beta
#16Earlier quoted context omitted.
All major OS already have a permission' system. It's on dropbox & co to honor them. On linux you can create an user group named "cloud", and allow dropbox to only sync files that belong to that group.
Except dropbox will be totally unaware and try to access it. What i envisionned was more like a "control center" app of all the outgoing (and incoming) pipes from your FS to syncing systems, with both last syncing time, configuration, etc. A little bit like what's already happening for mail and calendar integration into iOS applications, only for files and on the desktop.
Yes, right now Dropbox would probably crash, but that's their problem. I really don't think it's something that should be handled by the OS when they already have a solution for it.
Re: Dropbox ignore file or folder in beta
#17The most requested feature, to allow a file or folder to be ignored by Dropbox sync without using selective sync is finally in beta. The community requested a .dropboxignore file but they chose another solution which I’m sure is reasonable for making the feature more user friendly to non-devs. This will be immensely helpful for node_modules or build target directories.
> This will be immensely helpful for node_modules or build target directories. Why would anyone put a node project in Dropbox to begin with?
Putting every projects in Dropbox with .git is the most awesome feature of Dropbox. With Dropbox's History and Time Machine feature, you will be almost never able to delete/overwrite your work permanently, even by intention.
Re: Dropbox ignore file or folder in beta
#18The most requested feature, to allow a file or folder to be ignored by Dropbox sync without using selective sync is finally in beta. The community requested a .dropboxignore file but they chose another solution which I’m sure is reasonable for making the feature more user friendly to non-devs. This will be immensely helpful for node_modules or build target directories.
Who needs a VCS when you could just use Dropbox?
I don't do it personally, but I know people who do and it's not entirely illogical.
Re: Dropbox ignore file or folder in beta
#19Earlier quoted context omitted.
Except dropbox will be totally unaware and try to access it. What i envisionned was more like a "control center" app of all the outgoing (and incoming) pipes from your FS to syncing systems, with both last syncing time, configuration, etc. A little bit like what's already happening for mail and calendar integration into iOS applications, only for files and on the desktop.
Sorry, I edited my post before reading yours. Yes, right now Dropbox would probably crash, but that's their problem. I really don't think it's something that should be handled by the OS when they already have a solution for it.
Re: Dropbox ignore file or folder in beta
#20Earlier quoted context omitted.
I can imagine a world where a arbitrary directory is filled with gitignore, dropboxignore, googledriveignore, backblazeignore, s3ignore, rsynciginore, dotignore, ipfsignore . . . Goddamn, stop the world I want to get off
That's probably a clue something needs to be done at the OS level regarding FS integration with cloud syncing systems and permissions.
robots.txt didn't need to know about who the robot was or what the hosting server was.