files.com 1.1.199 → 1.1.201

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: '09256e6e311fa606fed83bfc48401d703ba9db06507739d12ff8eb2cfaff7ca7'
-  data.tar.gz: 6471f8433662c993b88403984ae202ece5b8a8a81fd819037cf2c75d012466b4
+  metadata.gz: 95c214f3aaac349f0d5695f3f700990d920c39d16e119214647d2c834c401de0
+  data.tar.gz: f51ca7563f8a4c2ba0d1aacc6214db6ba6895e96ac9399e979b0e29dd3008a5e
 SHA512:
-  metadata.gz: 51b9e07d5e01c915354388213a69196afa9c37607092bc477abe5835fd62d508e1931e52f4914b63df0f8b807fade3fa84db5e4c89309a49ba8bea6a46101674
-  data.tar.gz: efa3136546869d5fcf55df7771ee9109169b766c0fb431fa45477b34938f7da2e8a1c762bbcb29904de991f189974cad3652b2126b8c6b8314caa6e632f9f139
+  metadata.gz: 254a288f7e23fd32fa942a8f5f33bad5a878d6cd39467b0e05b9d0c23816982971729f931b5674b1845e3a0b30acec2cecccfccb00c309270552a67b1593ade3
+  data.tar.gz: 39815990c2fb01010749c5fab913b9a36bbf68bed2c14dccb1d25280dfc5828f2e410bcd6f1573a19c715dac56fdf63f3d800ad89cbd606bf4125d2abc126e71

data/README.md

@@ -51,12 +51,14 @@ To initiate a support conversation, you can send an [Authenticated Support Reque
 
 ## Authentication
 
+There are two ways to authenticate: API Key authentication and Session-based authentication.
+
 ### Authenticate with an API Key
 
 Authenticating with an API key is the recommended authentication method for most scenarios, and is
 the method used in the examples on this site.
 
-To use the API or SDKs with an API Key, first generate an API key from the [web
+To use an API Key, first generate an API key from the [web
 interface](https://www.files.com/docs/sdk-and-apis/api-keys) or [via the API or an
 SDK](/ruby/resources/developers/api-keys).
 
@@ -75,14 +77,14 @@ Don't forget to replace the placeholder, `YOUR_API_KEY`, with your actual API ke
 
 ### Authenticate with a Session
 
-You can also authenticate to the REST API or SDKs by creating a user session using the username and
+You can also authenticate by creating a user session using the username and
 password of an active user. If the user is an administrator, the session will have full access to
-the entire API. Sessions created from regular user accounts will only be able to access files that
+all capabilities of Files.com. Sessions created from regular user accounts will only be able to access files that
 user can access, and no access will be granted to site administration functions.
 
-API sessions use the exact same session timeout settings as web interface sessions. When an API
+Sessions use the exact same session timeout settings as web interface sessions. When a
 session times out, simply create a new session and resume where you left off. This process is not
-automatically handled by SDKs because we do not want to store password information in memory without
+automatically handled by our SDKs because we do not want to store password information in memory without
 your explicit consent.
 
 #### Logging In
@@ -122,6 +124,8 @@ session.destroy()
 
 ## Configuration
 
+The Ruby SDK is configured by setting attributes on the `Files` object.
+
 ### Configuration Options
 
 #### Base URL
@@ -166,7 +170,7 @@ Files.open_timeout = 60
 
 #### Read Timeout
 
-Read timeout in seconds. The default value is 80.
+Read timeout in seconds. The default value is 60.
 
 ```ruby title="Example setting"
 Files.read_timeout = 90

data/_VERSION

@@ -1 +1 @@
-1.1.199
+1.1.201

data/lib/files.com/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module Files
-  VERSION = "1.1.199"
+  VERSION = "1.1.201"
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: files.com
 version: !ruby/object:Gem::Version
-  version: 1.1.199
+  version: 1.1.201
 platform: ruby
 authors:
 - files.com
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2024-12-18 00:00:00.000000000 Z
+date: 2024-12-19 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: addressable