WIP re-documentation + etc.

[rigelrozanski]

Issues/Remaining

• IBC bash tests has a funny output which I think should be explained or not output:

/home/riger/go/src/github.com/tendermint/basecoin/tests/cli/shunit2: line 1058: 21687 Killed                  
${SERVER_EXE} relay start --chain1-id=$CHAIN_ID_1 --chain2-id=$CHAIN_ID_2 --chain1-addr=tcp://localhost:${PORT_1} --chain2-addr=tcp://localhost:${PORT_2} --from=$RELAY_KEY > ${BASE_DIR_1}/../relay.log

• IBC Docs need to be reviewed
• under go-basics consider using something other that GO-P2P in the example because that lib is depreciated

Completed:

• minor changes to install
• basecoin-basics
• basecoin-tool requires just a few small changes
• basecoin plugin page has been updated

[ethanfrey]

I thought I wrote this in the docs issue, but I guess not.

Bucky and I agreed on slack to remove the example plugin and just use counter for that purpose. It was a duplication of effort with no real reward. We can make counter plugin simpler if that is what is wished, but important to have a tested app with client and server

[rigelrozanski]

Roger thanks for the hot tip!

[rigelrozanski]

The only issue I had with using the counter as the example application was the filestructure of the counter app being fully mixed in with the basecoin file structure, this type of thing really confused me when I was working through the examples of ABCI many moons ago. So I've made an improvement. Everything is functionally the same, but the whole counter plugin is now located in docs/guide/counter Much easier to reference, much easier to copy and paste if you were going to program off of it. Downside is that it introduces one more line into make install. Overall I think having this plugin be separated makes the whole tutorial more succinct, and cleans up the main repo too, don't need to see all that counter jargon 90% of the time.

[ethanfrey]

Good idea with the counter reorg. It makes everything so much cleaner :)

[ethanfrey]

Okay, I managed to suppress the "killed" messages. Took me a deep dive into bash though, cuz it is not going to the stderr of any command, but rather the script itself.

https://stackoverflow.com/questions/5719030/bash-silently-kill-background-function-process

In the end, managed to disown these background processes, so the job messages don't print out.

[ethanfrey]

Closes #114