5 ms·
Who needs a VCS when you could just use Dropbox?
by chairmanwow1 7y ago
Who needs a VCS when you could just use Dropbox?
- positr0n 7y agoEven better, Dropbox as your VCS and database! https://www.reddit.com/r/sysadmin/comments/eaphr8/a_dropbox_account_gave_me_stomach_ulcers/ https://www.reddit.com/r/sysadmin/comments/eaphr8/a_dropbox_...
- jedieaston 7y agoThat story makes me want to become a goat farmer every time I read it, but, Dropbox must have intended that usage if they had a publicly available API, right?
- iudqnolq 7y agoAccording to TFA in parent Dropbox happily had them on a custom plan, charging them more and more as their data grew.
- pytester 7y agoAnybody who might want to back up uncommitted changes and files you can't check in to your repository? I don't do it personally, but I know people who do and it's not entirely illogical.
- deleted 7y ago[deleted]
- skocznymroczny 7y agoWhy use Dropbox if you could just use FTP + SVN/CVS? [1] [1] https://news.ycombinator.com/item?id=9224 https://news.ycombinator.com/item?id=9224
- mickael-kerjean 7y agoI did exactly that: https://github.com/mickael-kerjean/filestash https://github.com/mickael-kerjean/filestash As a side effect, it even supports .gitignore!
- michaelmior 7y agoDropbox as a VCS for separate documents intended to be accessed by non-technical users is not a terrible solution. Certainly there are better options, but I think something built on Dropbox could be workable in this case.