s3log 0.0.2 → 0.0.3

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: b693ca389fcecc5ee71f54f0c61e2f3f667a5ad1
-  data.tar.gz: 29d2bb97424735eae2d4e04ad924d8903ef204cc
+  metadata.gz: b1e1cf5759832d0b418f7a87e503e22ad6abc6c2
+  data.tar.gz: d7e95c7249c91bfd6b868f7b35d13fb6cf50f2fe
 SHA512:
-  metadata.gz: 66946073ad6f53919339bf88a433f28f94d95bdbb39222a099729a574b0c7f62e8109018be17bb766cc405ca894fbc2e414937a8c737889db8f67ef44cfd3e58
-  data.tar.gz: 4324aa991e1f0de6254f67594a63ce9f7dbb0a963a6a259993fbd6e14b3c1ab8ce37ac0b602400fc6c8e6738e220569081fa39c0a5172c9aaf90fb0a3cc00848
+  metadata.gz: f995e5e3fab29e773f7480a52241e9f1a448c08e2ca4b06c63529235d4e1c5f8d558ba7351238554483ce945ed50699e26cc0ca82f7a4f483948b85fd04389de
+  data.tar.gz: 0817870abf853d6f3d80558514c3931b10d0a555c7df7380553ba5b8767a6b469785041278c6c016789ff14e6ffc837d73c09c86fb1564d8640ffcd8b966f431

data/CHANGELOG.md

@@ -1,6 +1,10 @@
 S3log Changelog
 -------------------
 
+### v0.0.3 - 2014-01-15
+
+* refix on crontab scheduling for good this time
+
 ### v0.0.2 - 2014-01-15
 
 * fix on schedule command to generate a valid command

data/README.md

@@ -9,7 +9,7 @@ On S3 buckets you can activate logging, but the options are quite limited. You c
 
 S3log script is intended to transform this logging in a unified logfile wherever you need it, removing the logfiles from the logging bucket when they are downloaded.
 
-It's designed to run on debian/ubuntu servers but should work on any linux server, and it also work on mac osx.
+It's designed to run on debian/ubuntu servers but should work on any linux server, and it also work on mac osx. It works with ruby 1.9 and 2.0 (but not 1.8).
 
 (work in progress, not ready for use yet).
 
@@ -35,7 +35,7 @@ First you need to edit the config.yml file. The purpose is to have one config fi
 * logdir: the local dir where s3log logs are kept
 * loglevel: the level of logging. use warn for only error display, info to record info on operations, debug to have much more details
 * outputfile: the faile where the downloaded logs are going to be appended
-* schedule: the cron formatted frequency of downloading the logs from bucket ie. `0/5 * * * *`
+* schedule: the cron formatted frequency of downloading the logs from bucket ie. `*/5 * * * *`
 
 When your configuration is ready, veridy that it works with
 

data/lib/s3log/cron.rb

@@ -13,7 +13,7 @@ module S3log
     end
 
     def update
-      line = "#{@schedule} cd #{@path} && bash -l -c 'bundle exec s3log download -c #{@configfile} >> /dev/null 2>&1' # s3log_#{@jobname}\n"
+      line = "#{@schedule} bash -l -c 'cd #{@path} && bundle exec s3log download -c #{@configfile} >> /dev/null 2>&1' # s3log_#{@jobname}\n"
       tmp_cron_file = Tempfile.open('tmp_cron')
       included = false
       existing.each_line do |l|

data/lib/s3log/version.rb

@@ -1,3 +1,3 @@
 module S3log
-  VERSION = "0.0.2"
+  VERSION = "0.0.3"
 end

data/templates/s3log/config.yml

@@ -7,4 +7,4 @@ prefix: "somedir/prefix_" # the same as prefix stated in logging interface for t
 logdir: logs
 loglevel: info
 outputfile: s3.log
-schedule: "0/5 * * * *"
+schedule: "*/5 * * * *"

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: s3log
 version: !ruby/object:Gem::Version
-  version: 0.0.2
+  version: 0.0.3
 platform: ruby
 authors:
 - mose