Feature 1.6 (#63)

* add binary in the bin directory

* add binary in the bin directory

* move lib

* move lib

* test two branches

* test two branches

* test two branches

* test two branches

* test two branches 2

* add start time metric

* support syncing lua in RDB

* update redis-shake.darwin64

* update redis-shake.linux64

* fix log path bug

* fix log path bug

* add pid path

* fix README.md errors

* set parallel to 1 when not set

* modify code: enable heartbeat=0

* add some default settings

* remove src/github.com/kardianos/govendor

* support 5.0 rdb RDB_OPCODE_MODULE_AUX, RDB_OPCODE_IDLE and RDB_OPCODE_FREQ type

* add 1.2.2

* update, forget mix.go

* use restore to recovery key

* modify pid

* Create Dockerfile

* polish conf comment

* polish log

* polish conf

* set default parallel to 64

* v1.2.3: polish log print to print more error info

* update binary

* polish conf comment

* release v1.4: support rump type to using dump+restore command to syncing data

* polish ChangeLog

* polish ChangeLog2

* polish code

* add debug log of sending and receiving command

* add debug log of sending and receiving command2

* add debug log of sending and receiving command3

* improve rump to better fetch data from aliyun_cluster and tencent_cluster.

* add send and receiver id in debug

* improve rump to support fetching data from given keys in the file

* update binary

* add linux64 binary again

* polish README and comments

* modify source cluster of dump

* modify source cluster of rump

* modify source cluster of decode

* support fetching from cluster

* 1.source address supports cluster 2.target address supports several proxies to write data in a round-robin way.

* update .gitignore

* remove binary2

* polish

* polish READM again

* polish README again

README.md

@@ -40,7 +40,7 @@ m
 
 # Redis Type
 ---
-Both the source and target type can be standalone, opensource cluster and proxy. Although the architecture patterns of different vendors are different for the cluster architecture, we still support different cloud vendors like alibaba-cloud, tencent-cloud and so on.<br>
+Both the source and target type can be standalone, opensource cluster and proxy. Although the architecture patterns of different vendors are different for the proxy architecture, we still support different cloud vendors like alibaba-cloud, tencent-cloud and so on.<br>
 If the target is open source redis cluster, redis-shake uses [redis-go-cluster](https://github.com/chasex/redis-go-cluster) driver to write data. When target type is proxy, redis-shakes write data in round-robin way.<br>
 If the source is redis cluster, redis-shake launches multiple goroutines for parallel pull. User can use `rdb.parallel` to control the RDB syncing concurrency.<br>
 The "move slot" operations must be disabled on the source side.<br>