I do; actually I can start Yaws in embedded mode. I'm just wondering if there are differences between the two modes.

It's just that in one hand you have big install scripts and a lot of stuff that takes care of many things, on the other hand you have just to hit "make" and add ebin dir to your path. The only difference is that you have to write the config in plain erlang instead of .conf format. (Plus you gain more dynamic configuration). It feels too simple ... 


As an example, I see a "c_src" directory in Yaws. I don't know erlang runtime system very well but i see many things related to installation. Does embedded Yaws benefits from theese functionnalities (sendfile)  ?

I'm sorry if i'm way off the mark.


Thank you


Ludovic


> Message du 11/02/14 17:30
> De : "Steve Vinoski"
> A : "Ludovic Demblans"
> Copie à : "erlyaws-list"
> Objet : Re: [Erlyaws-list] Yaws embedded features
>
>


>


>
>

On Tue, Feb 11, 2014 at 11:27 AM, <l.demblans@laposte.net> wrote:
>

Hi everybody,


>

The Yaws docs provide useful information on building Yaws, and install

it system-wide or locally.


>

But it feels better to me to start it from another application with

application:start(yaws) or start_link the yaws supervisor, and provide

configuration as SConf and GConf records.


>

Someday I installed Yaws system wide with makefile commands and the

installation seemed to do a lot of stuff. Plus it seems there is a lot

of installation scripts on the github repository. I am wondering if I

am missing some features* or anything else when I choose to use Yaws

embedded.


>

Have you looked through this documentation:


>

http://yaws.hyber.org/embed.yaws


>

as well as chapter 12 here: http://yaws.hyber.org/yaws.pdf


>

--steve