A built release from source uses relative paths in the scripts to locate the various erlang start scripts it needs to run. If you are building from a rel instead of using the packages, the best thing to do is to move the entire 'rel/riak' directory somewhere as a unit. So you can move 'rel/riak' to something like /opt/riak then add /opt/riak/bin to your path. It is possible to move the rel/riak/bin, lib, data, etc directories separately, then adjusting the settings found in the rel/riak/etc/app.config.
Is there a particular reason you are building from source and installing versus using the packages? Good luck, Jared On Thu, Aug 29, 2013 at 8:23 PM, akonsu <ako...@gmail.com> wrote: > Hello, I have managed to successfully build riak from github source. In my > repository I now have rel/ directory. The guide at > http://docs.basho.com/riak/latest/ops/building/installing/post-install/ > instructs > to add the bin/directory to the PATH. My question is what files/directories > are actually needed? If I want to move the built release somewhere, what > files do I need to move? > > Thanks! > Konstantin > > _______________________________________________ > 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
