Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/carbonfive/boxdrop
Upload files to dropbox from the command line. Requires a dropbox app (https://www.dropbox.com/developers/apps).
https://github.com/carbonfive/boxdrop
Last synced: about 1 month ago
JSON representation
Upload files to dropbox from the command line. Requires a dropbox app (https://www.dropbox.com/developers/apps).
- Host: GitHub
- URL: https://github.com/carbonfive/boxdrop
- Owner: carbonfive
- License: other
- Created: 2012-01-14T02:01:23.000Z (almost 13 years ago)
- Default Branch: master
- Last Pushed: 2012-01-14T03:22:39.000Z (almost 13 years ago)
- Last Synced: 2024-04-15T12:18:26.784Z (9 months ago)
- Language: Ruby
- Homepage:
- Size: 93.8 KB
- Stars: 1
- Watchers: 83
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
Upload file to Dropbox from the command line.
Use of this gem requires that you have a dropbox app to support oauth authentication to your Dropbox account. See https://www.dropbox.com/developers/apps to create an app.
*Why?*
I want to distribute artifacts produced by builds on a continuous integration server via dropbox. That allows new artifacts to be automatically pushed to a number of dropbox users rather than requiring users to check for resources on a central server. It also allows me to use access to a common shared folder in dropbox to control distribution rather than managing another set of user credentials.
This could be accomplished by installing the dropbox client on the CI server and manipulating files on disk. However that would require that a number of distributed CI build agents all have the client installed and the same dropbox account authenticated. Instead I want a gem which will allow me to provide an authorized API key as part of my CI build configuration. This allows me to upload file on behalf of a different dropbox user account per project build by the CI server and depends only on the ability to manage the gems installed on each build agent, functionality the CI environment already provides, rather than installing a dropbox client package.
*Usage*
`DROPBOX_APP_KEY= DROPBOX_APP_SECRET= boxdrop authenticate`
`DROPBOX_APP_KEY= DROPBOX_APP_SECRET= DROPBOX_SESSION_KEY= DROPBOX_SESSION_SECRET= boxdrop `