dynamoid 0.7.1 → 1.0.0

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA1:
+  metadata.gz: 9a8130b39add7870e0217be2f31fc55808f02be5
+  data.tar.gz: 73f7caa9ae29e070fcae4deb87461f7a004d0470
+SHA512:
+  metadata.gz: 1e73c399b586b8c264f1b19dcb99e121705a82aaea2efcf68b4b250d1b35d30065ddd3c2fa213c6226260063dd8afd3beb6cd78a6ff7c1130fe92486544392ec
+  data.tar.gz: 89d9baede7e7b40c1e15ffa358b84199c8b5cdc9ea8fb855083da2b63651b1f8304b4afe845c0f7b9b1771a9957e0e0a57881663ad40d67542a0aaa9175605d7

data/Gemfile

@@ -1,24 +1,2 @@
-source "https://rubygems.org"
-
-gem 'activemodel'
-gem 'tzinfo'
-gem 'aws-sdk'
-
-# Add dependencies required to use your gem here.
-# Example:
-#   gem "activesupport", ">= 2.3.5"
-
-# Add dependencies to develop your gem here.
-# Include everything needed to run rake, tests, features, etc.
-group :development do
-  gem "rake"
-  gem "rspec"
-  gem "bundler"
-  gem "jeweler"
-  gem "yard"
-  gem "redcarpet", '1.17.2'
-  gem 'github-markup'
-  gem 'pry'
-  gem 'fake_dynamo', '~>0.1.3'
-  gem "mocha", '0.10.0'
-end
+source "http://www.rubygems.org"
+gemspec

data/README.markdown

@@ -15,82 +15,52 @@ But if you want a fast, scalable, simple, easy-to-use database (and a Gem that s
 Installing Dynamoid is pretty simple. First include the Gem in your Gemfile:
 
 ```ruby
-gem 'dynamoid'
+gem 'dynamoid', '~> 1'
 ```
 ## Prerequisities
 
-Dynamoid depends on  the aws-sdk, and this is tested on the current version of aws-sdk (1.6.9), rails 3.2.8.
+Dynamoid depends on the aws-sdk, and this is tested on the current version of aws-sdk (~> 2), rails (~> 4).
 Hence the configuration as needed for aws to work will be dealt with by aws setup.
 
 Here are the steps to setup aws-sdk.
 
 ```ruby
-gem 'aws-sdk'
+gem 'aws-sdk', '~>2'
 ```
-(or) include the aws-sdk in your Gemfile.
-
-
-[Refer this link for aws setup](https://github.com/amazonwebservices/aws-sdk-for-ruby)
 
-1. Just like the config/database.yml this file requires an entry for each environment, create config/aws.yml as follows:
-
-Fill in your AWS Access Key ID and Secret Access Key
-
-```ruby
-
-
-  development:
-    access_key_id: REPLACE_WITH_ACCESS_KEY_ID
-    secret_access_key: REPLACE_WITH_SECRET_ACCESS_KEY
-    dynamo_db_endpoint:  dynamodb.ap-southeast-1.amazonaws.com
-
-  test:
-    <<: *development
-
-  production:
-    <<: *development
+(or) include the aws-sdk in your Gemfile.
 
-```
+**NOTE:** Dynamoid-1.0 doesn't support aws-sdk Version 1 (Use Dynamoid Major Version 0 for aws-sdk 1)   
 
-(or)
+Configure AWS access:
+[Reference](https://github.com/aws/aws-sdk-ruby)
 
+For example, to configure AWS access:
 
-2. Create config/initializers/aws.rb as follows:
+Create config/initializers/aws.rb as follows:
 
 ```ruby
 
-#Additionally include any of the dynamodb paramters as needed.
-#(eg: if you would like to change the dynamodb endpoint, then add the parameter in
-# in the file  aws.yml or aws.rb
-
- AWS.config({
-    :access_key_id => 'REPLACE_WITH_ACCESS_KEY_ID',
-    :secret_access_key => 'REPLACE_WITH_SECRET_ACCESS_KEY',
-    :dynamo_db_endpoint => 'dynamodb.ap-southeast-1.amazonaws.com'
+  Aws.config.update({
+    region: 'us-west-2',
+    credentials: Aws::Credentials.new('REPLACE_WITH_ACCESS_KEY_ID', 'REPLACE_WITH_SECRET_ACCESS_KEY'),
   })
 
-
 ```
 
 For a full list of the DDB regions, you can go
 [here](http://docs.aws.amazon.com/general/latest/gr/rande.html#ddb_region).
 
-
-Refer to the documentation of the AWS module at the below link for all of the configuration options supported by DynamoDB.
-
-[Module AWS](http://docs.amazonwebservices.com/AWSRubySDK/latest/frames.html#!http%3A//docs.amazonwebservices.com/AWSRubySDK/latest/AWS.html)
-
 Then you need to initialize Dynamoid config to get it going. Put code similar to this somewhere (a Rails initializer would be a great place for this if you're using Rails):
 
 ```ruby
   Dynamoid.configure do |config|
-    config.adapter = 'aws_sdk' # This adapter establishes a connection to the DynamoDB servers using Amazon's own AWS gem.
+    config.adapter = 'aws_sdk_v2' # This adapter establishes a connection to the DynamoDB servers using Amazon's own AWS gem.
     config.namespace = "dynamoid_app_development" # To namespace tables created by Dynamoid from other tables you might have.
     config.warn_on_scan = true # Output a warning to the logger when you perform a scan rather than a query on a table.
-    config.partitioning = true # Spread writes randomly across the database. See "partitioning" below for more.
-    config.partition_size = 200  # Determine the key space size that writes are randomly spread across.
     config.read_capacity = 100 # Read capacity for your tables
     config.write_capacity = 20 # Write capacity for your tables
+    config.endpoint = 'http://localhost:3000' # [Optional]. If provided, it communicates with the DB listening at the endpoint. This is useful for testing with [Amazon Local DB] (http://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Tools.DynamoDBLocal.html). 
   end
 
 ```
@@ -126,7 +96,12 @@ These fields will not change an existing table: so specifying a new read_capacit
 
 You'll have to define all the fields on the model and the data type of each field. Every field on the object must be included here; if you miss any they'll be completely bypassed during DynamoDB's initialization and will not appear on the model objects.
 
-By default, fields are assumed to be of type ```:string```. But you can also use ```:integer```, ```:float```, ```:set```, ```:array```, ```:datetime```, ```:boolean```, and ```:serialized```. You get magic columns of id (string), created_at (datetime), and updated_at (datetime) for free.
+By default, fields are assumed to be of type ```:string```. Other built-in types are
+```:integer```, ```:number```, ```:set```, ```:array```, ```:datetime```, ```:boolean```, and ```:serialized```.
+If built-in types do not suit you, you can use a custom field type represented by an arbitrary class, provided that the class supports a compatible serialization interface.
+The primary use case for using a custom field type is to represent your business logic with high-level types, while ensuring portability or backward-compatibility of the serialized representation.
+
+You get magic columns of id (string), created_at (datetime), and updated_at (datetime) for free.
 
 ```ruby
 class User
@@ -135,32 +110,77 @@ class User
   field :name
   field :email
   field :rank, :integer
-  field :number, :float
+  field :number, :number
   field :joined_at, :datetime
   field :hash, :serialized
 
 end
 ```
 
-### Indexes
-
-You can also define indexes on fields, combinations of fields, and one range field. Yes, only one range field: in DynamoDB tables can have at most one range index, so make good use of it! To make an index, just specify the fields you want it on, either single or in an array. If the entire index is a range, pass ```:range => true```. Otherwise, pass the attribute that will become the range key. The only range attributes you can use right now are integers, floats, and datetimes. If you pass a string as a range key likely DynamoDB will complain a lot.
+You can optionally set a default value on a field using either a plain value or a lambda:
 
 ```ruby
-class User
-  include Dynamoid::Document
+  field :actions_taken, :integer, {default: 0}
+  field :joined_at, :datetime, {default: ->(){Time.now}}
+```
 
-  ...
+To use a custom type for a field, suppose you have a `Money` type.
 
-  index :name
-  index :email
-  index [:name, :email]
-  index :created_at, :range => true
-  index :name, :range_key => :joined_at
+```ruby
+  class Money
+    # ... your business logic ...
+    
+    def dynamoid_dump
+      "serialized representation as a string"
+    end
+    
+    def self.dynamoid_load(serialized_str)
+      # parse serialized representation and return a Money instance
+      Money.new(...)
+    end
+  end
+  
+  class User
+    include Dynamoid::Document
+    
+    field :balance, Money
+  end
+```
 
-end
+If you want to use a third-party class (which does not support `#dynamoid_dump` and `.dynamoid_load`)
+as your field type, you can use an adapter class providing `.dynamoid_dump` and `.dynamoid_load` class methods
+for your third-party class.  (`.dynamoid_load` can remain the same from the previous example; here we just
+add a level of indirection for serializing.)  Example:
+
+```ruby
+  # Third-party Money class
+  class Money; end
+  
+  class MoneyAdapter
+    def self.dynamoid_load(money_serialized_str)
+      Money.new(...)
+    end
+    
+    def self.dynamoid_dump(money_obj)
+      money_obj.value.to_s
+    end
+  end
+  
+  class User
+    include Dynamoid::Document
+    
+    field :balance, MoneyAdapter
+  end
 ```
 
+Lastly, you can control the data type of your custom-class-backed field at the DynamoDB level.
+This is especially important if you want to use your custom field as a numeric range or for
+number-oriented queries.  By default custom fields are persisted as a string attribute, but
+your custom class can override this with a `.dynamoid_field_type` class method, which would
+return either `:string` or `:number`.
+(DynamoDB supports some other attribute types, but Dynamoid yet does not.)
+
+
 ### Associations
 
 Just like in ActiveRecord (or your other favorite ORM), Dynamoid uses associations to create links between models.
@@ -245,7 +265,7 @@ Save forces persistence to the datastore: a unique ID is also assigned, but it i
 u.id # => "3a9f7216-4726-4aea-9fbc-8554ae9292cb"
 ```
 
-Along with persisting the model's attributes, indexes are automatically updated on save. To use associations, you use association methods very similar to ActiveRecord's:
+To use associations, you use association methods very similar to ActiveRecord's:
 
 ```ruby
 address = u.addresses.create
@@ -271,10 +291,10 @@ u.addresses.where(:city => 'Chicago').all
 
 But keep in mind Dynamoid -- and document-based storage systems in general -- are not drop-in replacements for existing relational databases. The above query does not efficiently perform a conditional join, but instead finds all the user's addresses and naively filters them in Ruby. For large associations this is a performance hit compared to relational database engines.
 
-You can also limit returned results, or select a record from which to start, to support pagination:
+You can also limit the number of evaluated records, or select a record from which to start, to support pagination:
 
 ```ruby
-Address.limit(5).start(address) # Only 5 addresses.
+Address.eval_limit(5).start(address) # Only 5 addresses.
 ```
 
 For large queries that return many rows, Dynamoid can use AWS' support for requesting documents in batches:
@@ -305,14 +325,6 @@ User.where("created_at.lt" => DateTime.now - 1.day).all
 
 It also supports .gte and .lte. Turning those into symbols and allowing a Rails SQL-style string syntax is in the works. You can only have one range argument per query, because of DynamoDB's inherent limitations, so use it sensibly!
 
-## Partitioning, Provisioning, and Performance
-
-DynamoDB achieves much of its speed by relying on a random pattern of writes and reads: internally, hash keys are distributed across servers, and reading from two consecutive servers is much faster than reading from the same server twice. Of course, many of our applications request one key (like a commonly used role, a superuser, or a very popular product) much more frequently than other keys. In DynamoDB, this will result in lowered throughput and slower response times, and is a design pattern we should try to avoid.
-
-Dynamoid attempts to obviate this problem transparently by employing a partitioning strategy to divide up keys randomly across DynamoDB's servers. Each ID is assigned an additional number (by default 0 to 199, but you can increase the partition size in Dynamoid's configuration) upon save; when read, all 200 hashes are retrieved simultaneously and the most recently updated one is returned to the application. This results in a significant net performance increase, and is usually invisible to the application itself. It does, however, bring up the important issue of provisioning your DynamoDB tables correctly.
-
-When your read or write throughput exceed your table's allowed provisioning, DynamoDB will wait on connections until throughput is available again. This will appear as very, very slow requests and can be somewhat frustrating. Partitioning significantly increases the amount of throughput tables will experience; though DynamoDB will ignore keys that don't exist, if you have 20 partitioned keys representing one object, all will be retrieved every time the object is requested. Ensure that your tables are set up for this kind of throughput, or turn provisioning off, to make sure that DynamoDB doesn't throttle your requests.
-
 ## Concurrency
 
 Dynamoid supports basic, ActiveRecord-like optimistic locking on save operations. Simply add a `lock_version` column to your table like so: 
@@ -327,10 +339,10 @@ class MyTable
 end
 ```
 
-In this example, all saves to `MyTable` will raise an `AWS::DynamoDB::Errors::ConditionalCheckFailedException` if a concurrent process loaded, edited, and saved the same row. Your code should trap this exception, reload the row (so that it will pick up the newest values), and try the save again. 
-
-Calls to `update` and `update!` also increment the `lock_version`, however they do not check the existing value. This guarantees that a update operation will raise an exception in a concurrent save operation, however a save operation will never cause an update to fail. Thus, `update` is useful & safe only for doing atomic operations (e.g. increment a value, add/remove from a set, etc), but should not be used in a read-modify-write pattern. 
+In this example, all saves to `MyTable` will raise an `Dynamoid::Errors::StaleObjectError` if a concurrent process loaded, edited, and saved the same row. Your code should trap this exception, reload the row (so that it will pick up the newest values), and try the save again.
 
+Calls to `update` and `update!` also increment the `lock_version`, however they do not check the existing value. This guarantees that a update operation will raise an exception in a concurrent save operation, however a save operation will never cause an update to fail. Thus, `update` is useful & safe only for doing atomic operations (e.g. increment a value, add/remove from a set, etc), but should not be used in a read-modify-write pattern.
+ 
 ## Credits
 
 Dynamoid borrows code, structure, and even its name very liberally from the truly amazing [Mongoid](https://github.com/mongoid/mongoid). Without Mongoid to crib from none of this would have been possible, and I hope they don't mind me reusing their very awesome ideas to make DynamoDB just as accessible to the Ruby world as MongoDB.
@@ -344,10 +356,14 @@ Also, without contributors the project wouldn't be nearly as awesome. So many th
 * [Jason Dew](https://github.com/jasondew)
 * [Luis Arias](https://github.com/luisantonioa)
 * [Stefan Neculai](https://github.com/stefanneculai)
+* [Philip White](https://github.com/philipmw)
+* [Peeyush Kumar](https://github.com/peeyush1234)
 
 ## Running the tests
 
-Running the tests is fairly simple. In one window, run `fake_dynamo --port 4567`, and in the other, use `rake`.
+Running the tests is fairly simple. In one window, run `bin/start_dynamodblocal`, and in the other, use `rake`.
+
+[![Build Status](https://travis-ci.org/Dynamoid/Dynamoid.svg)](https://travis-ci.org/Dynamoid/Dynamoid)
 
 ## Copyright
 

data/Rakefile

@@ -11,20 +11,6 @@ rescue Bundler::BundlerError => e
 end
 require 'rake'
 
-require 'jeweler'
-Jeweler::Tasks.new do |gem|
-  # gem is a Gem::Specification... see http://docs.rubygems.org/read/chapter/20 for more options
-  gem.name = "dynamoid"
-  gem.homepage = "http://github.com/Veraticus/Dynamoid"
-  gem.license = "MIT"
-  gem.summary = "Dynamoid is an ORM for Amazon's DynamoDB"
-  gem.description = "Dynamoid is an ORM for Amazon's DynamoDB that supports offline development, associations, querying, and everything else you'd expect from an ActiveRecord-style replacement."
-  gem.email = "josh@joshsymonds.com"
-  gem.authors = ["Josh Symonds"]
-  # dependencies defined in Gemfile
-end
-Jeweler::RubygemsDotOrgTasks.new
-
 require 'rspec/core'
 require 'rspec/core/rake_task'
 RSpec::Core::RakeTask.new(:spec) do |spec|
@@ -36,31 +22,19 @@ RSpec::Core::RakeTask.new(:rcov) do |spec|
   spec.rcov = true
 end
 
-desc "Start fake_dynamo, run tests, cleanup" 
+desc "Start DynamoDBLocal, run tests, clean up"
 task :unattended_spec do |t|
-  require 'tmpdir'
-  require 'socket'
-
-  dir = Dir.mktmpdir
-  data_file = File.join(dir, "data.fdb")
+  
+  if system('bin/start_dynamodblocal')
+    puts 'DynamoDBLocal started; proceeding with specs.'
+  else
+    raise 'Unable to start DynamoDBLocal.  Cannot run unattended specs.'
+  end
 
-  #Launch fake_dynamo
-  pid = Process.spawn'fake_dynamo', '-d', data_file, err: '/dev/null', out: '/dev/null'
   #Cleanup
-  at_exit {
-    Process.kill('TERM', pid)
-    FileUtils.rmtree(dir)
-  }
-  
-  #Wait for fake_dynamo to start taking requests
-  40.downto(0) do |count| #Wait up to 2 seconds
-    begin
-      s = TCPSocket.new 'localhost', 4567
-      s.close
-      break
-    rescue Errno::ECONNREFUSED
-      raise if(count == 0)
-      sleep 0.1
+  at_exit do
+    unless system('bin/stop_dynamodblocal')
+      $stderr.puts 'Unable to cleanly stop DynamoDBLocal.'
     end
   end
   

data/dynamoid.gemspec

@@ -1,208 +1,73 @@
-# Generated by jeweler
-# DO NOT EDIT THIS FILE DIRECTLY
-# Instead, edit Jeweler::Tasks in Rakefile, and run 'rake gemspec'
 # -*- encoding: utf-8 -*-
 
 Gem::Specification.new do |s|
   s.name = "dynamoid"
-  s.version = "0.7.1"
+  s.version = "1.0.0"
 
-  s.required_rubygems_version = Gem::Requirement.new(">= 0") if s.respond_to? :required_rubygems_version=
-  s.authors = ["Josh Symonds"]
-  s.date = "2013-08-05"
+  # Keep in sync with README
+  s.authors = %w(
+    Josh Symonds
+    Logan Bowers
+    Craig Heneveld
+    Anatha Kumaran
+    Jason Dew
+    Luis Arias
+    Stefan Neculai
+    Philip White
+    Peeyush Kumar
+  )
   s.description = "Dynamoid is an ORM for Amazon's DynamoDB that supports offline development, associations, querying, and everything else you'd expect from an ActiveRecord-style replacement."
-  s.email = "josh@joshsymonds.com"
   s.extra_rdoc_files = [
     "LICENSE.txt",
     "README.markdown"
   ]
-  s.files = [
-    ".document",
-    ".rspec",
-    ".travis.yml",
-    "Gemfile",
-    "Gemfile.lock",
-    "Gemfile_activemodel4",
-    "Gemfile_activemodel4.lock",
-    "LICENSE.txt",
-    "README.markdown",
-    "Rakefile",
-    "VERSION",
-    "doc/.nojekyll",
-    "doc/Dynamoid.html",
-    "doc/Dynamoid/Adapter.html",
-    "doc/Dynamoid/Adapter/AwsSdk.html",
-    "doc/Dynamoid/Adapter/Local.html",
-    "doc/Dynamoid/Associations.html",
-    "doc/Dynamoid/Associations/Association.html",
-    "doc/Dynamoid/Associations/BelongsTo.html",
-    "doc/Dynamoid/Associations/ClassMethods.html",
-    "doc/Dynamoid/Associations/HasAndBelongsToMany.html",
-    "doc/Dynamoid/Associations/HasMany.html",
-    "doc/Dynamoid/Associations/HasOne.html",
-    "doc/Dynamoid/Associations/ManyAssociation.html",
-    "doc/Dynamoid/Associations/SingleAssociation.html",
-    "doc/Dynamoid/Components.html",
-    "doc/Dynamoid/Config.html",
-    "doc/Dynamoid/Config/Options.html",
-    "doc/Dynamoid/Criteria.html",
-    "doc/Dynamoid/Criteria/Chain.html",
-    "doc/Dynamoid/Criteria/ClassMethods.html",
-    "doc/Dynamoid/Dirty.html",
-    "doc/Dynamoid/Dirty/ClassMethods.html",
-    "doc/Dynamoid/Document.html",
-    "doc/Dynamoid/Document/ClassMethods.html",
-    "doc/Dynamoid/Errors.html",
-    "doc/Dynamoid/Errors/ConditionalCheckFailedException.html",
-    "doc/Dynamoid/Errors/DocumentNotValid.html",
-    "doc/Dynamoid/Errors/Error.html",
-    "doc/Dynamoid/Errors/InvalidField.html",
-    "doc/Dynamoid/Errors/InvalidQuery.html",
-    "doc/Dynamoid/Errors/MissingRangeKey.html",
-    "doc/Dynamoid/Fields.html",
-    "doc/Dynamoid/Fields/ClassMethods.html",
-    "doc/Dynamoid/Finders.html",
-    "doc/Dynamoid/Finders/ClassMethods.html",
-    "doc/Dynamoid/IdentityMap.html",
-    "doc/Dynamoid/IdentityMap/ClassMethods.html",
-    "doc/Dynamoid/Indexes.html",
-    "doc/Dynamoid/Indexes/ClassMethods.html",
-    "doc/Dynamoid/Indexes/Index.html",
-    "doc/Dynamoid/Middleware.html",
-    "doc/Dynamoid/Middleware/IdentityMap.html",
-    "doc/Dynamoid/Persistence.html",
-    "doc/Dynamoid/Persistence/ClassMethods.html",
-    "doc/Dynamoid/Validations.html",
-    "doc/_index.html",
-    "doc/class_list.html",
-    "doc/css/common.css",
-    "doc/css/full_list.css",
-    "doc/css/style.css",
-    "doc/file.LICENSE.html",
-    "doc/file.README.html",
-    "doc/file_list.html",
-    "doc/frames.html",
-    "doc/index.html",
-    "doc/js/app.js",
-    "doc/js/full_list.js",
-    "doc/js/jquery.js",
-    "doc/method_list.html",
-    "doc/top-level-namespace.html",
-    "dynamoid.gemspec",
-    "lib/dynamoid.rb",
-    "lib/dynamoid/adapter.rb",
-    "lib/dynamoid/adapter/aws_sdk.rb",
-    "lib/dynamoid/associations.rb",
-    "lib/dynamoid/associations/association.rb",
-    "lib/dynamoid/associations/belongs_to.rb",
-    "lib/dynamoid/associations/has_and_belongs_to_many.rb",
-    "lib/dynamoid/associations/has_many.rb",
-    "lib/dynamoid/associations/has_one.rb",
-    "lib/dynamoid/associations/many_association.rb",
-    "lib/dynamoid/associations/single_association.rb",
-    "lib/dynamoid/components.rb",
-    "lib/dynamoid/config.rb",
-    "lib/dynamoid/config/options.rb",
-    "lib/dynamoid/criteria.rb",
-    "lib/dynamoid/criteria/chain.rb",
-    "lib/dynamoid/dirty.rb",
-    "lib/dynamoid/document.rb",
-    "lib/dynamoid/errors.rb",
-    "lib/dynamoid/fields.rb",
-    "lib/dynamoid/finders.rb",
-    "lib/dynamoid/identity_map.rb",
-    "lib/dynamoid/indexes.rb",
-    "lib/dynamoid/indexes/index.rb",
-    "lib/dynamoid/middleware/identity_map.rb",
-    "lib/dynamoid/persistence.rb",
-    "lib/dynamoid/validations.rb",
-    "spec/app/models/address.rb",
-    "spec/app/models/camel_case.rb",
-    "spec/app/models/car.rb",
-    "spec/app/models/magazine.rb",
-    "spec/app/models/message.rb",
-    "spec/app/models/nuclear_submarine.rb",
-    "spec/app/models/sponsor.rb",
-    "spec/app/models/subscription.rb",
-    "spec/app/models/tweet.rb",
-    "spec/app/models/user.rb",
-    "spec/app/models/vehicle.rb",
-    "spec/dynamoid/adapter/aws_sdk_spec.rb",
-    "spec/dynamoid/adapter_spec.rb",
-    "spec/dynamoid/associations/association_spec.rb",
-    "spec/dynamoid/associations/belongs_to_spec.rb",
-    "spec/dynamoid/associations/has_and_belongs_to_many_spec.rb",
-    "spec/dynamoid/associations/has_many_spec.rb",
-    "spec/dynamoid/associations/has_one_spec.rb",
-    "spec/dynamoid/associations_spec.rb",
-    "spec/dynamoid/config_spec.rb",
-    "spec/dynamoid/criteria/chain_spec.rb",
-    "spec/dynamoid/criteria_spec.rb",
-    "spec/dynamoid/dirty_spec.rb",
-    "spec/dynamoid/document_spec.rb",
-    "spec/dynamoid/fields_spec.rb",
-    "spec/dynamoid/finders_spec.rb",
-    "spec/dynamoid/identity_map_spec.rb",
-    "spec/dynamoid/indexes/index_spec.rb",
-    "spec/dynamoid/indexes_spec.rb",
-    "spec/dynamoid/persistence_spec.rb",
-    "spec/dynamoid/validations_spec.rb",
-    "spec/dynamoid_spec.rb",
-    "spec/spec_helper.rb",
-    "spec/support/with_partitioning.rb"
-  ]
-  s.homepage = "http://github.com/Veraticus/Dynamoid"
+  # file list is generated with `git ls-files | grep -v -E -e '^spec/' -e '^\.' -e 'bin/'`
+  s.files = %w(
+    Gemfile
+    LICENSE.txt
+    README.markdown
+    Rakefile
+    dynamoid.gemspec
+    lib/dynamoid.rb
+    lib/dynamoid/adapter.rb
+    lib/dynamoid/adapter_plugin/aws_sdk_v2.rb
+    lib/dynamoid/associations.rb
+    lib/dynamoid/associations/association.rb
+    lib/dynamoid/associations/belongs_to.rb
+    lib/dynamoid/associations/has_and_belongs_to_many.rb
+    lib/dynamoid/associations/has_many.rb
+    lib/dynamoid/associations/has_one.rb
+    lib/dynamoid/associations/many_association.rb
+    lib/dynamoid/associations/single_association.rb
+    lib/dynamoid/components.rb
+    lib/dynamoid/config.rb
+    lib/dynamoid/config/options.rb
+    lib/dynamoid/criteria.rb
+    lib/dynamoid/criteria/chain.rb
+    lib/dynamoid/dirty.rb
+    lib/dynamoid/document.rb
+    lib/dynamoid/errors.rb
+    lib/dynamoid/fields.rb
+    lib/dynamoid/finders.rb
+    lib/dynamoid/identity_map.rb
+    lib/dynamoid/middleware/identity_map.rb
+    lib/dynamoid/persistence.rb
+    lib/dynamoid/validations.rb
+  )
+  s.homepage = "http://github.com/Dynamoid/Dynamoid"
   s.licenses = ["MIT"]
   s.require_paths = ["lib"]
   s.rubygems_version = "1.8.24"
   s.summary = "Dynamoid is an ORM for Amazon's DynamoDB"
 
-  if s.respond_to? :specification_version then
-    s.specification_version = 3
-
-    if Gem::Version.new(Gem::VERSION) >= Gem::Version.new('1.2.0') then
-      s.add_runtime_dependency(%q<activemodel>, [">= 0"])
-      s.add_runtime_dependency(%q<tzinfo>, [">= 0"])
-      s.add_runtime_dependency(%q<aws-sdk>, [">= 0"])
-      s.add_development_dependency(%q<rake>, [">= 0"])
-      s.add_development_dependency(%q<rspec>, [">= 0"])
-      s.add_development_dependency(%q<bundler>, [">= 0"])
-      s.add_development_dependency(%q<jeweler>, [">= 0"])
-      s.add_development_dependency(%q<yard>, [">= 0"])
-      s.add_development_dependency(%q<redcarpet>, ["= 1.17.2"])
-      s.add_development_dependency(%q<github-markup>, [">= 0"])
-      s.add_development_dependency(%q<pry>, [">= 0"])
-      s.add_development_dependency(%q<fake_dynamo>, ["~> 0.1.3"])
-      s.add_development_dependency(%q<mocha>, ["= 0.10.0"])
-    else
-      s.add_dependency(%q<activemodel>, [">= 0"])
-      s.add_dependency(%q<tzinfo>, [">= 0"])
-      s.add_dependency(%q<aws-sdk>, [">= 0"])
-      s.add_dependency(%q<rake>, [">= 0"])
-      s.add_dependency(%q<rspec>, [">= 0"])
-      s.add_dependency(%q<bundler>, [">= 0"])
-      s.add_dependency(%q<jeweler>, [">= 0"])
-      s.add_dependency(%q<yard>, [">= 0"])
-      s.add_dependency(%q<redcarpet>, ["= 1.17.2"])
-      s.add_dependency(%q<github-markup>, [">= 0"])
-      s.add_dependency(%q<pry>, [">= 0"])
-      s.add_dependency(%q<fake_dynamo>, ["~> 0.1.3"])
-      s.add_dependency(%q<mocha>, ["= 0.10.0"])
-    end
-  else
-    s.add_dependency(%q<activemodel>, [">= 0"])
-    s.add_dependency(%q<tzinfo>, [">= 0"])
-    s.add_dependency(%q<aws-sdk>, [">= 0"])
-    s.add_dependency(%q<rake>, [">= 0"])
-    s.add_dependency(%q<rspec>, [">= 0"])
-    s.add_dependency(%q<bundler>, [">= 0"])
-    s.add_dependency(%q<jeweler>, [">= 0"])
-    s.add_dependency(%q<yard>, [">= 0"])
-    s.add_dependency(%q<redcarpet>, ["= 1.17.2"])
-    s.add_dependency(%q<github-markup>, [">= 0"])
-    s.add_dependency(%q<pry>, [">= 0"])
-    s.add_dependency(%q<fake_dynamo>, ["~> 0.1.3"])
-    s.add_dependency(%q<mocha>, ["= 0.10.0"])
-  end
+  s.add_runtime_dependency(%q<activemodel>, ["~> 4"])
+  s.add_runtime_dependency(%q<aws-sdk-resources>, ["~> 2"])
+  s.add_runtime_dependency(%q<concurrent-ruby>, ["~> 0.9"])
+  s.add_development_dependency(%q<rake>, [">= 0"])
+  s.add_development_dependency(%q<rspec>, ["~> 3"])
+  s.add_development_dependency(%q<bundler>, [">= 0"])
+  s.add_development_dependency(%q<yard>, [">= 0"])
+  s.add_development_dependency(%q<github-markup>, [">= 0"])
+  s.add_development_dependency(%q<pry>, [">= 0"])
 end