README.md in s3log-0.0.4 vs README.md in s3log-0.0.5
- old
+ new
@@ -1,9 +1,9 @@
# S3log
[![Gem Version](https://badge.fury.io/rb/s3log.png)](http://rubygems.org/gems/s3log)
-[![Dependency Status](https://gemnasium.com/eduvo/s3log.png)](https://gemnasium.com/eduvo/s3log)
+[![Dependency Status](https://gemnasium.com/mose/s3log.png)](https://gemnasium.com/eduvo/s3log)
Downloader for aws S3 logs and agglomerator.
On S3 buckets you can activate logging, but the options are quite limited. You can point the logging to another bucket in the same region only and logging will generate a lot of small logging files, and will not delete them. It's not very convenient for debugging.
@@ -48,10 +48,22 @@
s3log schedule -c another_config.yml
The `schedule` command will update the user crontab, that you can verify with `crontab -l`.
In all s3log commands if you don't specify the config file with `-c`, it will use `config.yml`.
+Here is how it is supposed to work:
+
+* first install s3log, init a dir, tune up config file
+* for my rails app I configure the s3.log output file to shared/log/ so it gets rotated like all other log files and backed up as well
+* launch a first download to grab all the files
+* it will download each file, append their content to the outputfile, then delete the downloaded file from the bucket
+* launch the schedule command to setup the cronjob, I like it every 5 minutes but it can be every minute if you want a real-time feeling
+* the subsequent downloads take 1 or 2s in my case
+* turn loglevel to debug for a while to verify that all goes according to the plan
+* turn loglevel back to info or warn depending to your need
+* go have a coffee and do something useful with your life
+
## Contributing
1. Fork it
2. Create your feature branch (`git checkout -b my-new-feature`)
3. Commit your changes (`git commit -am 'Add some feature'`)
@@ -63,5 +75,7 @@
* mose
## License
Copyright (c) 2014 Faria Systems Inc. distributed under MIT license
+Copyright (c) 2017 mose
+