Ah, ok - the github project gave me the impression you could bolt it into 1.0.2.
Have built a ring using HEAD and it's working now, thanks.
On 13 January 2012 15:00, Jeffrey Massung <j...@basho.com> wrote:
> Riak Control will only work within master and/or Riak 1.1+. There are
> changes within riak_core for riak_control. Control might compile just fine
> (and better! ;-)), but much tof the functionality it would need doesn't
> exist in prior versions.
>
> --
> Jeffrey Massung
> Software Engineer
> j...@basho.com
>
> On Jan 13, 2012, at 4:45 AM, Dick Davies wrote:
>
> Have tried shoehorning this into a 1.0.2 . The github docs seem to assume
> you already know how to extend risk, and I don't.
>
> Even without a t-shirt bribe :) am still curious what I'm missing here.
> https
> listener is up, but I don't have anything under /admin (and riak
>
> have got rebar to build the riak_control project, copied the built project
> into the lib/ folder within the riak installation
>
> (
> riak-1.0.2:$ ls -d lib/r*
> lib/riak_control lib/riak_kv-1.0.2 lib/riak_search-1.0.2 lib/riakc-1.2.0
> lib/riak_core-1.0.2 lib/riak_pipe-1.0.2 lib/riak_sysmon-1.0.0
> lib/runtime_tools-1.8.5
> riak-1.0.2:$
> )
> and added a block to my app.config
> (between the riak_core and riak_kv config blocks, see below) but the
> module isn't loading up
> after I stop/start the node:
>
> riak-1.0.2:$ ./bin/riak-admin status | grep riak_control
>
> is there an extra step?
>
> ...
> ...
> {platform_log_dir, "./log"}
> ]},
>
> %% riak control bit
> {riak_control, [
> {enabled, true},
> {auth, none},
> {admin, true}
> ]},
>
> %% Riak KV config
> {riak_kv, [
> %% Storage_
> ...
> ...
>
> _______________________________________________
> riak-users mailing list
> riak-users@lists.basho.com
> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
>
>
_______________________________________________
riak-users mailing list
riak-users@lists.basho.com
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
