This section may be ignored ; just leaving it here as it may apply still for a while - it referred to migrating from old to new kd (if you don't know what that even means, don't stress. Just jump to next section)]: it goes without saying that you have to deploy the daemon on both your old.koding as well as your new koding vm - the latter if you want to extract those data from within new kd itself
Let it warm up if it's a cold morning.
-
Download the linux x64 pkg:
cd ~ && wget -O - "https://www.dropbox.com/download?plat=lnx.x86_64" | tar xzf - -
Init daemon:
~/.dropbox-dist/dropboxd
You will see something like:
This client is not linked to any account... Please visit https://www.dropbox.com/cli_link?host_id=7d44a557aa5eggs85f2da0x67334d02c1 to link this machine.
Copypaste and load that link in another tab. Return and ctrl+c to end process. (optional but recommended)
wget -O ~/dropbox.py "http://www.dropbox.com/download?dl=packages/dropbox.py"
chmod 755 ~/dropbox.py<== I didn't have to but this couldn't hurt to do.
- You can now manipulate Dropbox using
python dropbox.pyor alias in PATH if you wish for a cleaner/easier setup.
I've had the above setup running on the now 'old.koding' for months. The one obvious use: there is more than enough space on a fresh dropbox to back up everything in your old.koding including the hidden (useless) dotfiles for thumbails in picture folders if you want to. Why the $#^% not?
Bonus:
you can even set it to run almost as a server-in-a-server (always online too) - it has a built in script for that; I found it not entirely foolproof.
But if you know your py/bash scripts (or even rb/haskell/js/perl/php - there are sdk's for these too and more languages via 3rd party devs) you can obviously cron it or whatever.
@leeolayvar know how to fork a gist?