mirror of
https://github.com/offen/docker-volume-backup.git
synced 2025-10-26 06:55:58 +08:00
1.9 KiB
1.9 KiB
| title | layout | parent | nav_order |
|---|---|---|---|
| Set up Dropbox storage backend | default | How Tos | 12 |
Set up Dropbox storage backend
Acquiring authentication tokens
- Create a new Dropbox App in the App Console
- Open your new Dropbox App and set
DROPBOX_APP_KEYandDROPBOX_APP_SECRETin your environment (e.g. docker-compose.yml) accordingly - Click on
Permissionsin your app and make sure, that the following permissions are cranted (or more):
files.metadata.writefiles.metadata.readfiles.content.writefiles.content.read
- Replace APPKEY in
https://www.dropbox.com/oauth2/authorize?client_id=APPKEY&token_access_type=offline&response_type=codewith the app key from step 2 - Visit the URL and confirm the access of your app. This gives you an
auth code-> save it somewhere! - Replace AUTHCODE, APPKEY, APPSECRET accordingly and perform the request:
curl https://api.dropbox.com/oauth2/token \
-d code=AUTHCODE \
-d grant_type=authorization_code \
-d client_id=APPKEY \
-d client_secret=APPSECRET
- Execute the request. You will get a JSON formatted reply. Use the value of the
refresh_tokenfor the last environment variableDROPBOX_REFRESH_TOKEN - You should now have
DROPBOX_APP_KEY,DROPBOX_APP_SECRETandDROPBOX_REFRESH_TOKENset. These don't expire.
Note: Using the "Generated access token" in the app console is not supported, as it is only very short lived and therefore not suitable for an automatic backup solution. The refresh token handles this automatically - the setup procedure above is only needed once.
Other parameters
Important: If you chose App folder access during the creation of your Dropbox app in step 1 above, you can only write in the app's directory!
This means, that DROPBOX_REMOTE_PATH must start with e.g. /Apps/YOUR_APP_NAME or /Apps/YOUR_APP_NAME/some_sub_dir