dynamoid 3.3.0 → 3.7.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: eac484a25ff6886d838773be1b34f1fa9c7a51bf75ec46ed93984e97f273575c
-  data.tar.gz: 349e23120b78776d352c576bd7ffe0d2d1a2b69b0b5107d81698435bcbe2fb2e
+  metadata.gz: 2146a1a188ecf2b8dd2f280172119879d6612d9eadda6cbcbf6defb3319f7022
+  data.tar.gz: df59300783324be7952fd25f8d49880707938762d3960ce1d422c18b49e26ac6
 SHA512:
-  metadata.gz: cdbe5b559ceea1a834c6bfdbd956bc0dcba57172be55a4003213dafdd54e702b8ae7c1f62f6a04c11f13f3f3907429cbff1e008ccfcef2b90e54b512c301b38f
-  data.tar.gz: 796c4496a3cabdde4433ee18797176d674e8be5ca887978d73792bea7fdf8cc0e697ca475c5b50cc972217524a6a006751f7497c84dbbe40a0a296bad5b1a79d
+  metadata.gz: d2ebd06729d024b98338e5c11953976935f5252ad76f6dec9265929fd447ed488295d9f06c8ae5440c7c6a494fb1cdb44ffeba002c18ea52bd4ad100df2d4c66
+  data.tar.gz: eddf03eb98125fbc7fcfa842e8276ba5dcbd558abacc3adeb2d451e3bb71bcb92f69eb84a01231304b4690b087a826ebf7c4ee2426a16d92a7a126ceddf1e132

data/CHANGELOG.md

@@ -1,13 +1,116 @@
 # HEAD
 
-## Breaking
+---
+
+
+
+# 3.7.0 / 2021-02-02
+
 
 ## Features
 
+* [#476](https://github.com/Dynamoid/dynamoid/pull/476) Added `#with_index` method to force an index in query (@bmalinconico)
+* [#481](https://github.com/Dynamoid/dynamoid/pull/481) Added `alias` option to the `field` method to declare a field alias and use more conventional name to set and get value
+
 ## Improvements
 
+* [#482](https://github.com/Dynamoid/dynamoid/pull/482) Support Ruby 3.0 and Rails 6.1
+* [#461](https://github.com/Dynamoid/dynamoid/pull/461) Allow to delete item attribute with `#update` method (@jkirsteins)
+* [#463](https://github.com/Dynamoid/dynamoid/pull/463) Raise `UnknownAttribute` exception when specified not declared attribute name (@AlexGascon)
+
 ## Fixes
 
+* [#480](https://github.com/Dynamoid/dynamoid/pull/480) Repair `.consistent`/`.delete_all`/`.destroy_all` calls directly on a model class
+* [#484](https://github.com/Dynamoid/dynamoid/pull/484) Fix broken foreign keys after model deleting (@kkan)
+* Fixes in Readme.md: [#470](https://github.com/Dynamoid/dynamoid/pull/470) (@rromanchuk), [#473](https://github.com/Dynamoid/dynamoid/pull/473) (@Rulikkk)
+
+---
+
+
+
+# 3.6.0 / 2020-07-13
+
+
+## Features
+
+* [#458](https://github.com/Dynamoid/dynamoid/pull/458) Added `binary` field type
+* [#459](https://github.com/Dynamoid/dynamoid/pull/459) Added `log_formatter` config option and changed default logging format
+
+## Improvements
+
+* [#423](https://github.com/Dynamoid/dynamoid/pull/423) Added warning when generated for a field methods override existing ones
+* [#429](https://github.com/Dynamoid/dynamoid/pull/429) Added `raise_error` option for `find` method
+* [#440](https://github.com/Dynamoid/dynamoid/pull/440) Optimized performance of `first` method when there are only conditions on key attribute in a query (@mrkamel)
+* [#445](https://github.com/Dynamoid/dynamoid/pull/445) Support `limit` parameter in `first` method (@mrkamel)
+* [#450](https://github.com/Dynamoid/dynamoid/pull/450) Got rid of `null-logger` gem to make Dynamoid dependencies license suitable for commercial use (@yakjuly)
+* [#454](https://github.com/Dynamoid/dynamoid/pull/454) Added block argument to `create`/`create!` methods
+* [#456](https://github.com/Dynamoid/dynamoid/pull/456) Detect when `find` method requires a range key argument and raise `Dynamoid::Errors::MissingRangeKey` exception if it's missing
+* YARD documentation:
+  * added missing documentation so now all the public methods are documented
+  * hid all the private methods and classes
+
+## Fixes
+
+* [#425](https://github.com/Dynamoid/dynamoid/pull/425) Fixed typos in the README.md file (@omarsotillo)
+* [#432](https://github.com/Dynamoid/dynamoid/pull/432) Support tables that use "hash_key" as their partition key name (@remomueller)
+* [#434](https://github.com/Dynamoid/dynamoid/pull/434) Support tables that have attribute with name "range_value"
+* [#453](https://github.com/Dynamoid/dynamoid/pull/453) Fixed issue with using `type` attribute as a GSI hash key
+
+---
+
+
+
+# 3.5.0 / 2020-04-04
+
+
+## Features
+* Feature: [#405](https://github.com/Dynamoid/dynamoid/pull/405) Added `update!` class method (@UrsaDK)
+* Feature: [#408](https://github.com/Dynamoid/dynamoid/pull/408) Added `ActiveSupport` load hook on `Dynamoid` load (@aaronmallen)
+* Feature: [#422](https://github.com/Dynamoid/dynamoid/pull/422) Added `.pluck` method
+
+## Fixes:
+* Fix: [#410](https://github.com/Dynamoid/dynamoid/pull/410) Fixed creating GSI when table uses on-demand capacity provisioning (@icy-arctic-fox)
+* Fix: [#414](https://github.com/Dynamoid/dynamoid/pull/414) Fixed lazy table creation
+* Fix: [#415](https://github.com/Dynamoid/dynamoid/pull/415) Fixed RubyDoc comment (@walkersumida)
+* Fix: [#420](https://github.com/Dynamoid/dynamoid/pull/420) Fixed `#persisted?` for deleted/destroyed models
+
+## Improvements:
+* Improvement: [#416](https://github.com/Dynamoid/dynamoid/pull/416) Improved speed of Adapter's `truncate` method. It now uses `#batch_delete_item` method (@TheSmartnik)
+* Improvement: [#421](https://github.com/Dynamoid/dynamoid/pull/421) Added `touch: false` option of the #save method
+* Improvement: [#423](https://github.com/Dynamoid/dynamoid/pull/423) Added warning when generated for a field methods override existing ones
+
+---
+
+
+
+# 3.4.1
+
+## Fixes
+* Fix: [#398](https://github.com/Dynamoid/dynamoid/pull/398) Fix broken configuration
+
+---
+
+
+
+# 3.4.0
+
+## Features
+* Feature: [#386](https://github.com/Dynamoid/dynamoid/pull/386) Disable timestamps fields on a table level with new
+  table option `timestamps`
+* Feature: [#387](https://github.com/Dynamoid/dynamoid/pull/387) Add TTL support with table option `expires`
+* Feature: [#393](https://github.com/Dynamoid/dynamoid/pull/393) Support pre-configured credentials with new config
+  option `credentials` (@emmajhyde)
+* Feature: [#397](https://github.com/Dynamoid/dynamoid/pull/397) Configure on-demand table capacity mode with `capacity_mode` option
+
+## Improvements
+* Improvement: [#388](https://github.com/Dynamoid/dynamoid/pull/388) Minor memory optimization - don't allocate excessive
+  hash (@arjes)
+
+## Fixes
+
+* Fix: [#382](https://github.com/Dynamoid/dynamoid/pull/382) Fixed deprecation warning about `Module#parent_name` in Rails 6 (@tmandke)
+* Fix: Typos in Readme.md (@romeuhcf)
+
 ---
 
 

data/README.md

@@ -34,7 +34,7 @@ Gemfile:
 ```ruby
 gem 'dynamoid'
 ```
-## Prerequisities
+## Prerequisites
 
 Dynamoid depends on the aws-sdk, and this is tested on the current
 version of aws-sdk (~> 3), rails (>= 4). Hence the configuration as
@@ -80,6 +80,27 @@ Dynamoid.configure do |config|
 end
 ```
 
+Additionally, if you would like to pass in pre-configured AWS credentials
+(e.g. you have an IAM role credential, you configure your credentials
+elsewhere in your project, etc.), you may do so:
+
+```ruby
+require 'dynamoid'
+
+credentials = Aws::AssumeRoleCredentials.new(
+    region: region,
+    access_key_id: key,
+    secret_access_key: secret,
+    role_arn: role_arn,
+    role_session_name: 'our-session'
+  )
+
+Dynamoid.configure do |config|
+  config.region = 'us-west-2',
+  config.credentials = credentials
+end
+```
+
 For a full list of the DDB regions, you can go
 [here](http://docs.aws.amazon.com/general/latest/gr/rande.html#ddb_region).
 
@@ -105,8 +126,8 @@ end
 Dynamoid supports Ruby >= 2.3 and Rails >= 4.2.
 
 Its compatibility is tested against following Ruby versions: 2.3, 2.4,
-2.5 and 2.6, JRuby 9.2.8.0 and against Rails versions: 4.2, 5.0, 5.1,
-5.2 and 6.0.
+2.5, 2.6, 2.7 and 3.0, JRuby 9.2.x and against Rails versions: 4.2, 5.0, 5.1,
+5.2, 6.0 and 6.1.
 
 ## Setup
 
@@ -143,6 +164,47 @@ won't change its hash key, which it expects will be `user_id`. If this
 table doesn't exist yet, however, Dynamoid will create it with these
 options.
 
+There is a basic support of DynamoDB's [Time To Live (TTL)
+mechanism](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/TTL.html).
+If you declare a field as TTL field - it will be initialised if doesn't
+have value yet. Default value is current time + specified seconds.
+
+```ruby
+class User
+  include Dynamoid::Document
+
+  table expires: { field: :ttl, after: 60 }
+
+  field :ttl, :integer
+end
+```
+
+Field used to store expiration time (e.g. `ttl`) should be declared
+explicitly and should have numeric type (`integer`, `number`) only.
+`datetime` type is also possible but only if it's stored as number
+(there is a way to store time as a string also).
+
+It's also possible to override a global option `Dynamoid::Config.timestamps`
+on a table level:
+
+```ruby
+table timestamps: false
+```
+
+This option controls generation of timestamp fields
+`created_at`/`updated_at`.
+
+It's also possible to override table capacity mode configured globally
+with table level option `capacity_mode`. Valid values are
+`:provisioned`, `:on_demand` and `nil`:
+
+```ruby
+table capacity_mode: :on_demand
+```
+
+If table capacity mode is on-demand, another related table-level options
+`read_capacity` and `write_capacity` will be ignored.
+
 ### Fields
 
 You'll have to define all the fields on the model and the data type of
@@ -150,27 +212,28 @@ 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`. Other built-in
-types are `:integer`, `:number`, `:set`, `:array`, `:map`, `:datetime`,
-`date`, `:boolean`, `:raw` and `:serialized`. `array` and `map` match
-List and Map DynamoDB types respectively. `raw` type means you can store
-Ruby Array, Hash, String and numbers. 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.
+By default, fields are assumed to be of type `string`. Other built-in
+types are `integer`, `number`, `set`, `array`, `map`, `datetime`,
+`date`, `boolean`, `binary`, `raw` and `serialized`. `array` and
+`map` match List and Map DynamoDB types respectively. `raw` type means
+you can store Ruby Array, Hash, String and numbers. 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.
 
 #### Note on boolean type
 
 The boolean fields are stored as DynamoDB boolean values by default.
 Dynamoid can store boolean values as strings as well - `'t'` and `'f'`.
-So if you want to change default format of boolean field you can easily
-achieve this with `store_as_native_boolean` field option:
+So if you want to change the default format of boolean field you can
+easily achieve this with `store_as_native_boolean` field option:
 
 ```ruby
 class Document
-  include DynamoId::Document
+  include Dynamoid::Document
 
   field :active, :boolean, store_as_native_boolean: false
 end
@@ -184,7 +247,7 @@ strings instead then set `store_as_string` to `true`
 
 ```ruby
 class Document
-  include DynamoId::Document
+  include Dynamoid::Document
 
   field :sent_on, :date, store_as_string: true
 end
@@ -199,7 +262,7 @@ as ISO-8601 formatted strings instead then set `store_as_string` to
 
 ```ruby
 class Document
-  include DynamoId::Document
+  include Dynamoid::Document
 
   field :sent_at, :datetime, store_as_string: true
 end
@@ -231,7 +294,7 @@ types.
 
 ```ruby
 class Document
-  include DynamoId::Document
+  include Dynamoid::Document
 
   field :tags, :set, of: :integer
 end
@@ -243,7 +306,7 @@ elements type:
 
 ```ruby
 class Document
-  include DynamoId::Document
+  include Dynamoid::Document
 
   field :values, :set, of: { serialized: { serializer: JSON } }
   field :dates, :set, of: { date: { store_as_string: true } }
@@ -267,7 +330,7 @@ natively, you should specify element type with `of` option:
 
 ```ruby
 class Document
-  include DynamoId::Document
+  include Dynamoid::Document
 
   field :dates, :array, of: :date
 end
@@ -302,6 +365,26 @@ field :actions_taken, :integer, default: 0
 field :joined_at, :datetime, default: -> { Time.now }
 ```
 
+#### Aliases
+
+It might be helpful to define an alias for already existing field when
+naming convention used for a table differs from conventions common in
+Ruby:
+
+```ruby
+field firstName, :string, alias: :first_name
+```
+
+This way there will be generated
+setters/getters/`<name>?`/`<name>_before_type_cast` methods for both
+original field name (`firstName`) and an alias (`first_name`).
+
+```ruby
+user = User.new(first_name: 'Michael')
+user.first_name # => 'Michael'
+user.firstName # => 'Michael'
+```
+
 #### Custom Types
 
 To use a custom type for a field, suppose you have a `Money` type.
@@ -513,7 +596,7 @@ c.my_new_type
 
 ### Type casting
 
-Dynamid supports type casting and tryes to do it in the most convinient
+Dynamoid supports type casting and tries to do it in the most convenient
 way. Values for all fields (except custom type) are coerced to declared
 field types.
 
@@ -551,7 +634,7 @@ well.
 
 ### Dirty API
 
-Dynamoid supports Dirty API which equvalents to [Rails 5.2
+Dynamoid supports Dirty API which is equivalent to [Rails 5.2
 `ActiveModel::Dirty`](https://api.rubyonrails.org/v5.2/classes/ActiveModel/Dirty.html).
 There is only one limitation - change in place of field isn't detected
 automatically.
@@ -569,7 +652,7 @@ u.email = 'josh@joshsymonds.com'
 u.save
 ```
 
-Save forces persistence to the datastore: a unique ID is also assigned,
+Save forces persistence to the data store: a unique ID is also assigned,
 but it is a string and not an auto-incrementing number.
 
 ```ruby
@@ -624,7 +707,7 @@ to relational database engines.
 
 **WARNING:** There is a limitation of conditions passed to `where`
 method. Only one condition for some particular field could be specified.
-The last one only will be applyed and others will be ignored. E.g. in
+The last one only will be applied and others will be ignored. E.g. in
 examples:
 
 ```ruby
@@ -700,7 +783,7 @@ for requesting documents in batches:
 
 ```ruby
 # Do some maintenance on the entire table without flooding DynamoDB
-Address.all(batch_size: 100).each { |address| address.do_some_work; sleep(0.01) }
+Address.batch(100).each { |address| address.do_some_work; sleep(0.01) }
 Address.record_limit(10_000).batch(100).each { … } # Batch specified as part of a chain
 ```
 
@@ -714,7 +797,7 @@ commands.
 At times it can be useful to rely on DynamoDB [low-level
 pagination](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Query.html#Query.Pagination)
 instead of fixed pages sizes. Each page results in a single Query or
-Scan call to DyanmoDB, but returns an unknown number of records.
+Scan call to DynamoDB, but returns an unknown number of records.
 
 Access to the native DynamoDB pages can be obtained via the
 `find_by_pages` method, which yields arrays of records.
@@ -729,7 +812,7 @@ is a hash including a key `:last_evaluated_key`. The value of this key
 can be used for the `start` method to fetch the next page of records.
 
 This way it can be used for instance to implement efficiently pagination
-in web-application:
+in web-applications:
 
 ```ruby
 class UserController < ApplicationController
@@ -774,7 +857,7 @@ Address.where('postcode.null': false)
 Address.where('postcode.not_null': true)
 ```
 
-**WARNING:** Please take into accout that `NULL` and `NOT_NULL`
+**WARNING:** Please take into account that `NULL` and `NOT_NULL`
 operators check attribute presence in a document, not value. So if
 attribute `postcode`'s value is `NULL`, `NULL` operator will return
 false because attribute exists even if has `NULL` value.
@@ -831,7 +914,7 @@ 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
+have one range argument per query, because of DynamoDB inherent
 limitations, so use it sensibly!
 
 
@@ -839,7 +922,7 @@ limitations, so use it sensibly!
 
 In order to update document you can use high level methods
 `#update_attributes`, `#update_attribute` and `.update`. They run
-validation and collbacks.
+validation and callbacks.
 
 ```ruby
 Address.find(id).update_attributes(city: 'Chicago')
@@ -855,12 +938,12 @@ it runs `update` callbacks). All of them support conditional updates.
 doesn't exist.
 
 ```ruby
-Adderess.find(id).update do |i|
+Address.find(id).update do |i|
   i.set city: 'Chicago'
   i.add latitude: 100
   i.delete set_of_numbers: 10
 end
-Adderess.find(id).update(if: { deliverable: true }) do |i|
+Address.find(id).update(if: { deliverable: true }) do |i|
   i.set city: 'Chicago'
 end
 Address.update_fields(id, city: 'Chicago')
@@ -872,7 +955,7 @@ Address.upsert(id, { city: 'Chicago' }, if: { deliverable: true })
 ### Deleting
 
 In order to delete some items `delete_all` method should be used. Any
-callback wont be called. Items delete in efficient way in batch.
+callback won't be called. Items delete in efficient way in batch.
 
 ```ruby
 Address.where(city: 'London').delete_all
@@ -893,17 +976,17 @@ class User
 end
 ```
 
-There are following options:
+There are the following options:
 * `hash_key` - is used as hash key of an index,
 * `range_key` - is used as range key of an index,
 * `projected_attributes` - list of fields to store in an index or has a
-  predefiled value `:keys_only`, `:all`; `:keys_only` is a default,
+  predefined value `:keys_only`, `:all`; `:keys_only` is a default,
 * `name` - an index will be created with this name when a table is
   created; by default name is generated and contains table name and keys
   names,
-* `read_capacity` - is used when table creates and used as an index
+* `read_capacity` - is used when table created and used as an index
   capacity; by default equals `Dynamoid::Config.read_capacity`,
-* `write_capacity` - is used when table creates and used as an index
+* `write_capacity` - is used when table created and used as an index
   capacity; by default equals `Dynamoid::Config.write_capacity`
 
 The only mandatory option is `name`.
@@ -954,7 +1037,7 @@ on the base table*
 
 Listed below are all configuration options.
 
-* `adapter` - usefull only for the gem developers to switch to a new
+* `adapter` - useful only for the gem developers to switch to a new
   adapter. Default and the only available value is `aws_sdk_v3`
 * `namespace` - prefix for table names, default is
   `dynamoid_#{application_name}_#{environment}` for Rails application
@@ -962,15 +1045,21 @@ Listed below are all configuration options.
 * `logger` - by default it's a `Rails.logger` in Rails application and
   `stdout` otherwise. You can disable logging by setting `nil` or
   `false` values. Set `true` value to use defaults
-* `access_key` - DynamoDb custom credentials for AWS, override global
-  AWS credentials if they present
-* `secret_key` - DynamoDb custom credentials for AWS, override global
-  AWS credentials if they present
+* `access_key` - DynamoDb custom access key for AWS credentials, override global
+  AWS credentials if they're present
+* `secret_key` - DynamoDb custom secret key for AWS credentials, override global
+  AWS credentials if they're present
+* `credentials` - DynamoDb custom pre-configured credentials, override global
+  AWS credentials if they're present
 * `region` - DynamoDb custom credentials for AWS, override global AWS
-  credentials if they present
+  credentials if they're present
 * `batch_size` - when you try to load multiple items at once with
 * `batch_get_item` call Dynamoid loads them not with one api call but
   piece by piece. Default is 100 items
+* `capacity_mode` - used at a table creation and means whether a table
+  read/write capacity mode will be on-demand or provisioned. Allowed
+  values are `:on_demand` and `:provisioned`. Default value is `nil` which
+  means provisioned mode will be used.
 * `read_capacity` - is used at table or indices creation. Default is 100
   (units)
 * `write_capacity` - is used at table or indices creation. Default is 20
@@ -984,7 +1073,7 @@ Listed below are all configuration options.
   when referring to them. Isn't thread safe. Default is `false`.
   `Use Dynamoid::Middleware::IdentityMap` to clear identity map for each HTTP request
 * `timestamps` - by default Dynamoid sets `created_at` and `updated_at`
-  fields for model at creation and updating. You can disable this
+  fields for model creation and updating. You can disable this
   behavior by setting `false` value
 * `sync_retry_max_times` - when Dynamoid creates or deletes table
   synchronously it checks for completion specified times. Default is 60
@@ -1000,7 +1089,7 @@ Listed below are all configuration options.
 * `models_dir` - `dynamoid:create_tables` rake task loads DynamoDb
   models from this directory. Default is `./app/models`.
 * `application_timezone` - Dynamoid converts all `datetime` fields to
-* specified time zone when loads data from the storage.
+  specified time zone when loads data from the storage.
   Acceptable values - `:utc`, `:local` (to use system time zone) and
   time zone name e.g. `Eastern Time (US & Canada)`. Default is `utc`
 * `dynamodb_timezone` - When a datetime field is stored in string format
@@ -1020,11 +1109,16 @@ Listed below are all configuration options.
   `nil`
 * `backoff_strategies`: is a hash and contains all available strategies.
   Default is { constant: ..., exponential: ...}
+* `log_formatter`: overrides default AWS SDK formatter. There are
+  several canned formatters: `Aws::Log::Formatter.default`,
+  `Aws::Log::Formatter.colored` and `Aws::Log::Formatter.short`. Please
+  look into `Aws::Log::Formatter` AWS SDK documentation in order to
+  provide own formatter.
 * `http_continue_timeout`: The number of seconds to wait for a
   100-continue HTTP response before sending the request body. Default
   option value is `nil`. If not specified effected value is `1`
 * `http_idle_timeout`: The number of seconds an HTTP connection is
-  allowed to sit idble before it is considered stale. Default option
+  allowed to sit idle before it is considered stale. Default option
   value is `nil`. If not specified effected value is `5`
 * `http_open_timeout`: The number of seconds to wait when opening a HTTP
   session. Default option value is `nil`. If not specified effected
@@ -1056,7 +1150,7 @@ 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
+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.
@@ -1102,7 +1196,7 @@ Dynamoid.configure do |config|
 end
 ```
 
-You can use your own strategy in following way:
+You can use your own strategy in the following way:
 
 ```ruby
 Dynamoid.configure do |config|
@@ -1193,7 +1287,7 @@ class User
 end
 
 Dynamoid.config.logger.level = :debug
-Dynamoid.config.endpoint = 'localhost:8000'
+Dynamoid.config.endpoint = 'http://localhost:8000'
 
 User.create(name: 'Alex')
 
@@ -1268,12 +1362,12 @@ environment.
 
 If you want to run all the specs that travis runs, use `bundle exec
 wwtd`, but first you will need to setup all the rubies, for each of `%w(
-2.0.0-p648 2.1.10 2.2.6 2.3.3 2.4.1 jruby-9.1.8.0 )`. When you run
+2.3.8 2.4.6 2.5.5 2.6.3 2.7.0 3.0.0 9.2.14.0)`. When you run
 `bundle exec wwtd` it will take care of starting and stopping the local
 dynamodb instance.
 
 ```shell
-rvm use 2.0.0-p648
+rvm use 3.0.0
 gem install rubygems-update
 gem install bundler
 bundle install