paperclip-dropbox 1.1.2 → 1.1.3

data/README.md

@@ -1,50 +1,20 @@
 # Dropbox
 
 This gem extends [Paperclip](https://github.com/thoughtbot/paperclip) with
-Dropbox storage.
+[Dropbox](https://www.dropbox.com) storage.
 
 ## Installation
 
-Put it in your `Gemfile`:
-
-```ruby
-gem "paperclip-dropbox"
+```sh
+$ gem install paperclip-dropbox
 ```
 
-And run `bundle install`.
-
 ## Dropbox Setup
 
 You must [create a Dropbox app](https://www.dropbox.com/developers/apps) and
 authorize it to access the Dropbox account you want to use for storage. You have
-a choice of two access types: **App folder** or **Full Dropbox**.
-
-### "Full Dropbox" access
-
-Files will be stored in the [Public folder](https://www.dropbox.com/help/16/en).
-Download URLs are predictable, valid forever, and don't require an API call to
-retrieve, but this may not be a good thing if you don't want your files to be
-easily accessed. When using one account to store data for multiple sites (e.g.
-staging and production instances), it's up to you to make sure they don't step
-on each other's toes.
-
-Note that accounts created after October 4, 2012 don't have the Public folder
-enabled by default: [Go here](https://www.dropbox.com/enable_public_folder) to
-enable it. If you get a message that the folder is deleted, just create a folder
-in the root named "Public", and it should gain the special icon.
-
-### "App folder" access
-
-Files will be stored in a subfolder under Apps (configurable in the app
-settings). Download URLs are generated on demand by calling the Dropbox API, and
-are only valid for 4 hours. This means your files are slightly "less public",
-and you can isolate data from multiple sites by creating multiple apps.
-
-**In app folder mode, every call to `#url` on an attachment will result in an
-HTTP request to Dropbox.** Whether or not this is acceptable will depend on what
-you're storing and how you're exposing it to users.
-
-### Authorizing your app
+a choice of two access types: **App folder** or **Full Dropbox**. You can read
+about the differences in [this wiki](https://github.com/janko-m/paperclip-dropbox/wiki/Access-types).
 
 After creating your app, it will have an "App key" and "App secret". Provide
 these and the access type (`dropbox` or `app_folder`) to the authorization Rake task:
@@ -53,8 +23,8 @@ these and the access type (`dropbox` or `app_folder`) to the authorization Rake
 $ rake dropbox:authorize APP_KEY=your_app_key APP_SECRET=your_app_secret ACCESS_TYPE=your_access_type
 ```
 
-It will output an authorization URL that you must visit to grant the app access.
-It will then output your access token, access token secret, and user ID.
+First it will give you an authorization URL that you must visit to grant the app access.
+Then it will output your **access token**, and **user ID**.
 
 For non-Rails projects, you must require this task in your `Rakefile`:
 
@@ -84,23 +54,28 @@ authorization Rake task.
 
 Example `config/dropbox.yml`:
 
+```yaml
+app_key: "APP_KEY"
+app_secret: "APP_SECRET"
+access_token: "ACCESS_TOKEN"
+access_token_secret: "ACCESS_TOKEN_SECRET"
+user_id: "USER_ID"
+access_type: "ACCESS_TYPE"
+```
+
+Of course, replace these strings with real values. The `"ACCESS_TYPE"`
+must be either `"dropbox"` or `"app_folder"` depending on the access
+type of your app; see **Dropbox Setup** above. If you're keeping your
+credentials in environment variables (or something similar), you can also use
+ERB:
+
 ```erb
 app_key: <%= ENV["DROPBOX_APP_KEY"] %>
-app_secret: <%= ENV["DROPBOX_APP_SECRET"] %>
-access_token: <%= ENV["DROPBOX_ACCESS_TOKEN"] %>
-access_token_secret: <%= ENV["DROPBOX_ACCESS_TOKEN_SECRET"] %>
-user_id: <%= ENV["DROPBOX_USER_ID"] %>
-access_type: <%= ENV["DROPBOX_ACCESS_TYPE"] %>
 ```
 
-It is good practice to not include the credentials directly in the YAML file.
-Instead you can set them in environment variables and embed them with ERB. Note
-`access_type` must be either `"dropbox"` or `"app_folder"` depending on the
-access type of your app; see **Dropbox Setup** above.
-
 You can also nest your credentials in environments (like in your `database.yml`):
 
-```erb
+```yaml
 development:
   app_key: "..."
   ...
@@ -167,6 +142,15 @@ When using `app_folder` access type, `#url` always returns a direct link, and
 setting the `:download` option simply forces the file to be downloaded even if
 the browser would normally just display it.
 
+### Check if the file exists
+
+You can easily check if the file exists on Dropbox:
+
+```ruby
+user.avatar.exists?
+# user.avatar.exists?(style)
+```
+
 ## License
 
-[MIT License](https://github.com/janko-m/paperclip-dropbox/blob/master/LICENSE)
+[MIT License](LICENSE)

data/lib/paperclip/storage/dropbox.rb

@@ -37,7 +37,7 @@ module Paperclip
         @queued_for_delete = []
       end
 
-      def exists?(style)
+      def exists?(style = default_style)
         metadata = dropbox_metadata(style)
         !metadata.nil? && !metadata['is_deleted']
       rescue DropboxError

data/paperclip-dropbox.gemspec

@@ -2,7 +2,7 @@
 
 Gem::Specification.new do |gem|
   gem.name          = "paperclip-dropbox"
-  gem.version       = "1.1.2"
+  gem.version       = "1.1.3"
   gem.platform      = Gem::Platform::RUBY
 
   gem.homepage      = "https://github.com/janko-m/paperclip-dropbox"

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: paperclip-dropbox
 version: !ruby/object:Gem::Version
-  version: 1.1.2
+  version: 1.1.3
   prerelease: 
 platform: ruby
 authors:
@@ -9,7 +9,7 @@ authors:
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2013-02-12 00:00:00.000000000 Z
+date: 2013-04-26 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: paperclip
@@ -208,7 +208,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
       version: '0'
       segments:
       - 0
-      hash: 569081523
+      hash: 503150639
 requirements: []
 rubyforge_project: 
 rubygems_version: 1.8.23