I have written a very usable configuration system called tconfig. For configuring tercio. I have also built in a pretty basic but working http server for use during development. This system is based off of the trap exit howto "A fast web server demonstrating some undocumented Erlang features". It's called 'carre' and built into the tercio system. Its not the only way to serve tercio apps but its by far the easiest. The configuration and briding systems are built of a custom, fast implementation of a json parser thats just a bit more lenient on input then the currently available one. It also can't parse chunked data, but there is always a trade off.