Running "rebar generate" now creates a self-contained yaws system under the build directory's "rel" subdirectory. The yaws script it provides at ./rel/yaws/bin/yaws isn't the same as the normal yaws script (the one normally found at ./bin/yaws); rather, it's a special script that starts yaws and the Erlang applications on which it depends as a local self-contained Erlang node. You can run ./rel/yaws/bin/yaws console to start an interactive yaws node, or ./rel/yaws/bin/yaws start to run it as a daemon, which you can later stop with ./rel/yaws/bin/yaws stop This script does not accept the command-line options that ./bin/yaws does, at least for now. If this is a problem, please raise an issue at the Yaws github repo or on the Yaws mailing list.
A "rebar compile" used to install yaws, yaws.conf, and other files under the user's home directory, just like "make local_install". This approach isn't idiomatic to rebar usage, so change it to install files locally under the build directory. Starting ./bin/yaws from the build directory starts this local installation.
Remove our copy of ibrowse in our test directory from git control. Instead, download ibrowse master from github if we don't have a fresh copy. Track master HEAD to make sure we have the latest. Change test/Makefile to fetch ibrowse if needed as part of building the "all" target. Add test/ibrowse to .gitignore.
… status' a lot more readable.