README.md in logstash-codec-avro-0.1.0 vs README.md in logstash-codec-avro-0.1.1
- old
+ new
@@ -1,66 +1,95 @@
-Logstash Avro Codec
-===================
+# Logstash Plugin
-How to Install
---------------
+This is a plugin for [Logstash](https://github.com/elasticsearch/logstash).
+It is fully free and fully open source. The license is Apache 2.0, meaning you are pretty much free to use it however you want in whatever way.
+
+## Documentation
+
+Logstash provides infrastructure to automatically generate documentation for this plugin. We use the asciidoc format to write documentation so any comments in the source code will be first converted into asciidoc and then into html. All plugin documentation are placed under one [central location](http://www.elasticsearch.org/guide/en/logstash/current/).
+
+- For formatting code or config example, you can use the asciidoc `[source,ruby]` directive
+- For more asciidoc formatting tips, see the excellent reference here https://github.com/elasticsearch/docs#asciidoc-guide
+
+## Need Help?
+
+Need help? Try #logstash on freenode IRC or the logstash-users@googlegroups.com mailing list.
+
+## Developing
+
+### 1. Plugin Developement and Testing
+
+#### Code
+- To get started, you'll need JRuby with the Bundler gem installed.
+
+- Create a new plugin or clone and existing from the GitHub [logstash-plugins](https://github.com/logstash-plugins) organization.
+
+- Install dependencies
+```sh
+bundle install
```
-bin/plugin install logstash-avro-codec
-```
-How to Use
-----------
-You can use this codec to decode avro messages
-in a Kafka topic input.
+#### Test
-Here is an example schema for tweets.
+```sh
+bundle exec rspec
+```
-### tweet.avsc
+The Logstash code required to run the tests/specs is specified in the `Gemfile` by the line similar to:
+```ruby
+gem "logstash", :github => "elasticsearch/logstash", :branch => "1.5"
```
-{
- "type" : "record",
- "name" : "twitter_schema",
- "namespace" : "com.miguno.avro",
- "fields" : [ {
- "name" : "username",
- "type" : "string",
- "doc" : "Name of the user account on Twitter.com"
- }, {
- "name" : "tweet",
- "type" : "string",
- "doc" : "The content of the user's Twitter message"
- }, {
- "name" : "timestamp",
- "type" : "long",
- "doc" : "Unix epoch time in seconds"
- } ],
- "doc:" : "A basic schema for storing Twitter messages"
-}
+To test against another version or a local Logstash, edit the `Gemfile` to specify an alternative location, for example:
+```ruby
+gem "logstash", :github => "elasticsearch/logstash", :ref => "master"
```
+```ruby
+gem "logstash", :path => "/your/local/logstash"
+```
-Along with the logstash config for reading in messages of this
-type using the avro codec with the logstash-input-kafka plugin.
+Then update your dependencies and run your tests:
-### logstash.conf
-
+```sh
+bundle install
+bundle exec rspec
```
-input {
- kafka {
- topic_id => 'test_topic'
- codec => avro {
- schema_file => 'tweet.avsc'
- }
- }
-}
-output {
- stdout {
- codec => rubydebug
- }
-}
+### 2. Running your unpublished Plugin in Logstash
+
+#### 2.1 Run in a local Logstash clone
+
+- Edit Logstash `tools/Gemfile` and add the local plugin path, for example:
+```ruby
+gem "logstash-filter-awesome", :path => "/your/local/logstash-filter-awesome"
```
+- Update Logstash dependencies
+```sh
+rake vendor:gems
+```
+- Run Logstash with your plugin
+```sh
+bin/logstash -e 'filter {awesome {}}'
+```
+At this point any modifications to the plugin code will be applied to this local Logstash setup. After modifying the plugin, simply rerun Logstash.
-### Running the setup
+#### 2.2 Run in an installed Logstash
+
+- Build your plugin gem
+```sh
+gem build logstash-filter-awesome.gemspec
```
-bin/logstash -f logstash.conf
+- Install the plugin from the Logstash home
+```sh
+bin/plugin install /your/local/plugin/logstash-filter-awesome.gem
```
+- Start Logstash and proceed to test the plugin
+
+## Contributing
+
+All contributions are welcome: ideas, patches, documentation, bug reports, complaints, and even something you drew up on a napkin.
+
+Programming is not a required skill. Whatever you've seen about open source and maintainers or community members saying "send patches or die" - you will not see that here.
+
+It is more important to me that you are able to contribute.
+
+For more information about contributing, see the [CONTRIBUTING](https://github.com/elasticsearch/logstash/blob/master/CONTRIBUTING.md) file.