Ryan Scott Brown

Tested locally, the changes work for me.

Hey, sorry for leaving you hanging on your question. To explain: When you first create the stack, you have a dep tree like this: ``` IAM::Policy -> DependsOn -> IAM::Role...

It would be nice to support a kwarg-style `key=value` to make it easy to do interactively for simple alphanumeric pairs. The verbose Key=mykey,Value= should only be for cases where you've...

I think more important than splitting it into utilities would be logically splitting it into subcommands the way `git` or `hg` do it.

What about naming it something like "cog", short for "cjdns on golang". It's short and easy to type.

I don't think that makes sense for default behavior, but I could see there being a "-k" or "--keys" option.

This sounds like a problem with your Go path. Check the contents of your $GOROOT environment variable. You can do this by doing `export PATH="$PATH:$GOROOT/bin"`

Ok, so make sure you have "$GOPATH" set, and run `go get github.com/inhies/cjdcmd` Check that `$PATH` contains your Go binaries directory ($GOPATH/bin) and then it should work.

Can you try going through http://golangtutorials.blogspot.com/2011/05/checking-we-have-go-setup-right.html ? It has more specific instructions that I gave.

That's fair, feel free to skip the indexing. Even without the index, JSONB should make a performance difference. Thank you for considering the change, and thanks for publishing these benchmarks....