> > a. Any documentation that shows how to properly deploy your erlang > code with the riak cluster (I'm currently writing a module, storing it > with riak_core, adding it to riak_core.app, and it's building fine, > can call it from riak console.)
http://wiki.basho.com/Configuration-Files.html#add_paths Assuming you compiled your Erlang module to an 'ebin' directory, a portion of your app.config might look like this: %% other configs... {riak_kv, [ %% ... {add_paths, ["/path/to/your/ebin"]}, %% ... ]}, %% ... Alternatively you can use the '-pz' switch in vm.args to add a path to the code loading directories. (See also: http://www.erlang.org/doc/man/erl.html) > b. The correct way to call an erlang function from the REST api or via > Ripple, specifically we are using the output of a Javascript Map to an > Erlang Reduce (If this is not supported, please let us know!) > Dan covered the proper way to do that in Ripple, but I might add that the output of your JavaScript phase must make sense to the Erlang phase; that bit is up to you. Sean Cribbs <[email protected]> Developer Advocate Basho Technologies, Inc. http://basho.com/ _______________________________________________ riak-users mailing list [email protected] http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
