…block. Technically this isn't required to make HTTPS work as Riak currently looks by default in the ./etc/ directory for the key and certificate files, but these should be exposed in the default generated app.config so the values can be tuned easily after node/cluster creation.
…the test server. Ref seancribbs/ripple#256
…uires https) Added a section to configure_ports in node/configuration which sets up https access if it hasn't already been defined or if riak_control was set to enabled. riak/cluster also had to be modified to handle proper incrementing of the min_port value.
The defaults for Node wouldn't ouput a valid app.config for created nodes because the username/password combinations are supposed to be represented as Erlang tuples, but instead they were defined as Ruby hashes.
…configured, rather than just checking versions.
… ('0.5.7' > '0.13.2'); I replaced the string comparison with Gem::Version for the comparison check
…rom client initialization
Also adds version ranges so we can avoid testing Luwak on 1.1+.
…ending if test server fails.
…ill be fixed in Riak 1.1, hopefully.