README.md in zabbix-ruby-client-0.0.17 vs README.md in zabbix-ruby-client-0.0.18

@@ -89,14 +89,17 @@
     * args [ eth0 ] is just the interface identifier
   * apt (uses ubuntu /usr/lib/update-notifier/apt-check) this one will populate the 'tag' field in host info, and is supposed to run every few hours or at least not every minute [apt_tpl](master/zabbix-templates/apt_tpl.xml)
   * sysinfo (uses uname -a) is populating the host info in the inventory, and should be ran at setup and/or monthly [sysinfo_tpl](master/zabbix-templates/sysinfo_tpl.xml)
 * apache (depends on mod_status with status_extended on) [apache_tpl](master/zabbix-templates/apache_tpl.xml)
 * mysql (uses mysqladmin extended-status) [mysql_tpl](master/zabbix-templates/mysql_tpl.xml)
+* postgres (uses psql and pg_stat_database) [postgres_tpl](master/zabbix-templates/postgres_tpl.xml)
+  * best is to use a .pgpass file see http://www.postgresql.org/docs/9.0/interactive/libpq-pgpass.html
 * nginx (requires httpStubStatus nginx module) [nginx_tpl](master/zabbix-templates/nginx_tpl.xml)
 * redis (uses redis-cli info) [redis_tpl](master/zabbix-templates/redis_tpl.xml)
   * args [ "/path/to/redis-cli", "options to connect" ]
 
+
 You can add extra plugins in a plugins/ dir in the working dir, just by copying one of the existing plugins in the repo and change to your need. All plugins present in plugins/ will be loaded if present in the config file you use. That can be convenient to test by using the -t flag, for example `bundle exec zrc -t testplugin.yml` where testplugin.yml only contains the name and args for yoiur plugin.
 
 ## Custom plugins how-to
 
 With the default config there is a plugins/ dir specified where you can put your own custom plugins. Those plugins need at least one `collect(*args)` method and optionaly a `discover(*args)` if this plugins plays the discover role.
@@ -157,11 +160,11 @@
 
 ```
 sudo useradd -m -r -s /bin/false -d /usr/local/zabtunnel zabtunnel
 ```
 
-On the zabbix server I created a key that I transfered to the clients in `/usr/local/zabtunnel/,ssh/authorized_keys`
+On the zabbix server I created a key that I transfered to the clients in `/usr/local/zabtunnel/.ssh/authorized_keys`
 
 ```
 sudo su -s /bin/bash - zabtunnel
 ssh-keygen
 ```
@@ -195,28 +198,22 @@
 ListenIP 127.0.0.1
 ```
 
 ## Todo
 
-* read /proc rather than rely on installed tools (done)
-* write tests
+* improve templates for graphs
 * add more plugins
   * memcache
-  * redis
   * mysql master/slave
+  * postgres replication
   * monit
   * passenger
-  * nginx (done)
   * logged users
   * denyhosts
   * postfix
   * sendgrid
   * airbrake
-  * disk occupation (done)
 * try to work out a way to create host/graphs/alerts from the client using Zabbix API
-* verify compatibility with ruby 1.9 (done)
-* create a resend system that will store timed data on client if connection to server fails, and will send pending (missed) data on next batch.
-
 
 ## Contributing
 
 1. Fork it
 2. Create your feature branch (`git checkout -b my-new-feature`)