Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I must admit that the first time I looked at Dropbox, the single folder design made me stop the train. It wasn't until months later that I realized I could set up symlinks. It was a bit of an "I feel like a dumbass" moment.

With this in mind, it's easy to see that the Dropbox made the right design decision. With symlinks, the problem was already solved for them in a way that power users are already familiar with.



Dropbox and symlinks is what I do with config files like .bashrc, .vimrc, .gitconfig, etc.

Then when you setup a new machine - install dropbox and let it sync, then just symlink them back up... everything is back to normal.

Really a nice setup so you can continue to change your config files and not worry about saving the changes to some backup gist or something


So the problem Drew mentioned, of mapping between different sets of sync folders on different machines, is transformed into mapping an identical folder hierarchy (i.e. the dropbox folder and contents) to arbitrary sync files/folders, done by the user, for that specific machine.

You get the simple, instant user model (dropbox folder), which you can customize to any arbitrary user model, as much or as little as you want, when you want it. And simple syncing.


I just keep my config files in git. Having to commit changes is a good thing, not a nuisance - being able to track changes is hugely useful.


Can you elaborate?


Take a look at the Wiki article on symlinks: http://en.wikipedia.org/wiki/Symbolic_link

If you're a Windows user think of a more hardcode version of shortcuts. You can create them in Windows Vista / 7 from the command line through the `mklink` command.

Basically you can set up a symbolic link from inside your Dropbox folder to any other directory and Dropbox will start syncing the folder without you having to actually copy or move files.





Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: