rails-cron-logger 1.0.0 → 1.0.1

data/README.md

@@ -22,4 +22,8 @@ Example:
 
     1 * * * * rails runner '$stdout.sync = true; <your code here>'
 
-Setting `$stdout.sync = true` in this gem seems like it would be a bit overreaching.
+Setting `$stdout.sync = true` in this gem seems a bit overreaching, but for convenience if you pass `:sync => true` to Logger.new then rails-cron-logger will perform this step for you.
+
+Example:
+
+    logger = RailsCronLogger::Logger.new(:sync => true)

data/lib/rails-cron-logger.rb

@@ -3,7 +3,16 @@ require 'rails-cron-logger/version'
 
 module RailsCronLogger
   class Logger < Logger
-    def initialize
+    def initialize(options={})
+      if options[:sync]
+        # Flushes output on every write to avoid losing valuable output if the cron job crashes, etc.
+        # see http://coderrr.wordpress.com/2008/12/20/automatically-flushing-redirected-or-piped-stdout/
+        # Note that this is obviously an interpreter-wide setting we're changing here.
+        # Really this ought to be set at a higher level than the code calling this logger (in the crontab
+        # or in the crontab script that calls your code perhaps) but adding an option here for convenience.
+        $stdout.sync = true
+      end
+
       logdev = if Rails.env.test?
                  # don't want log messages for tests mixed in with test output
                  Rails.application.config.paths.log.first

data/lib/rails-cron-logger/version.rb

@@ -1,7 +1,7 @@
 module Rails
   module Cron
     module Logger
-      VERSION = "1.0.0"
+      VERSION = "1.0.1"
     end
   end
 end

metadata

@@ -1,13 +1,13 @@
 --- !ruby/object:Gem::Specification 
 name: rails-cron-logger
 version: !ruby/object:Gem::Version 
-  hash: 23
+  hash: 21
   prerelease: 
   segments: 
   - 1
   - 0
-  - 0
-  version: 1.0.0
+  - 1
+  version: 1.0.1
 platform: ruby
 authors: 
 - Jordan Brough