s3_log 0.0.3 → 0.0.4

checksums.yaml

@@ -1,15 +1,15 @@
 ---
 !binary "U0hBMQ==":
   metadata.gz: !binary |-
-    ZWJmNzc4YmUzYWY1YmEzNGJiZmE1OGFmM2I3ZDZkMWI1ZmZjNTQ3NA==
+    MWM3NzM1NmY4YzRiMTFmZGU5MDYyMGM1MGU1M2VmNWU1MWIxNjc4Mg==
   data.tar.gz: !binary |-
-    MTY1MGYzZmU5NWFjZmI2NjMwM2U5M2NiM2ZmZmZmMzczYWRjYzkzMQ==
+    OWYzOTZkM2ZiMWE2MTljODU0MDczYzJkNjMwNzg1NzhmNDczMWU3ZA==
 SHA512:
   metadata.gz: !binary |-
-    ZjQyYzEwNGM0NDBjYTUxNTdhYWFiNDU3YWNjOTViMjFmM2ZhNTdhZWI3NTI5
-    ZmE3NjRlYWEzOTk0NjA1YmM0ZmY2ZDU1MjFkNDM2OTA2NjUwNDg2NGJhM2Jk
-    OTY1MDhjOWViMWQzMTg2OTg5YjVmOTMwOWI4MmNiMTgxOWRlOGY=
+    ZGM1OGY5M2RmM2UxMmI4YTAxZjg1MzFjOWVkNjJiN2UyZWY1MjJjZmY1NzU3
+    ZGNmOTE4OGFmYTgzNGM4NjI3MjI1OTI0MmI3MDUyZjVhYWU4MTU1N2NkMmI3
+    MTU2MjU5MjAxYjk2MDk3YTVhMTc5ZGRiZGI4ZTE1YjhkMDYzOTA=
   data.tar.gz: !binary |-
-    OWZlZDdhODM4MDJmNjY1OTBhODk1YmQ0YmE5MTcwZWVjYmQxYzBmNjU3NTU0
-    NjQ5ZjUyYmUwYjQ2ODMwYzQyODJiYjFkOGI3NTgwYmQ4M2VkNjI4ZDRmNTE4
-    NTZjNGU4MjM2NjY5ZjZiYmEwYTY0MzU1NWEyYzI2MGQxNWZkYjQ=
+    YjcyZjc3NzYxOTNlOWFmMDQyYjE2M2FiNmEwYzdhNjFkZTc5MmViNzgzOTU4
+    MmYyN2Q5NjhiNTdkNmJmN2FjODYyY2FjYTQxMThkZTRjMjY2NGUwZDU5MDY2
+    ZjUzZmE4YzJhNjllYWNmMzA4MzAwMWFlNTNmZDJiZTlhZjM3ZTg=

data/HISTORY.md

@@ -1,5 +1,6 @@
 ## History ##
 
+* 0.0.4 - Even more README reference fixes
 * 0.0.3 - Fixed README to remove s3_logger references
 * 0.0.2 - Renamed to S3Log to avoid conflict with an existing gem
 * 0.0.1 - Initial release

data/README.md

@@ -1,4 +1,4 @@
-## S3Logger ##
+## S3Log ##
 
 Naively log events to a file on S3
 
@@ -13,10 +13,10 @@ gem 's3_log'
 
 ## Configuration ##
 
-S3Logger requires an AWS access key id, AWS secret access key, and a S3 bucket (preferably created in advance) name to function. It can be configured (in a Rails initializer or what have you) like so:
+S3Log requires an AWS access key id, AWS secret access key, and a S3 bucket (preferably created in advance) name to function. It can be configured (in a Rails initializer or what have you) like so:
 
 ```ruby
-S3Logger.configure(
+S3Log.configure(
   access_key_id: 'YOUR AWS ACCESS KEY ID',
   secret_access_key: 'YOUR AWS SECRET ACCESS KEY',
   bucket: 'YOUR S3 BUCKET'
@@ -25,10 +25,10 @@ S3Logger.configure(
 
 ## Usage ##
 
-Basically, logging an event is a matter of using S3Logger.write to write content to a given file location on S3. The file does not have to exist prior to writing, and a write always appends to an existing file.
+Basically, logging an event is a matter of using S3Log.write to write content to a given file location on S3. The file does not have to exist prior to writing, and a write always appends to an existing file.
 
 ```ruby
-S3Logger.write('path/to/file', 'Some content')
+S3Log.write('path/to/file', 'Some content')
 ```
 
 ## Caveats ##
@@ -46,7 +46,7 @@ The actual library docs can be read
 ## Contributing ##
 
 Do you use git-flow? I sure do. Please base anything you do off of
-[the develop branch](https://github.com/ess/s3_logger/tree/develop).
+[the develop branch](https://github.com/ess/s3_log/tree/develop).
 
 1. Fork it.
 2. Perform some BDD magic. Seriously. Be testing.

data/lib/s3_log/version.rb

@@ -1,3 +1,3 @@
 module S3Log
-  VERSION = '0.0.3'
+  VERSION = '0.0.4'
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: s3_log
 version: !ruby/object:Gem::Version
-  version: 0.0.3
+  version: 0.0.4
 platform: ruby
 authors:
 - Dennis Walters