On Tue, Mar 25, 2014 at 7:36 AM, <l.demblans@laposte.net> wrote:

I'm trying to compile Yaws on webfaction (hosting service) with rebar, and it doesn't work because they don't have pam-devel or libpam or whatever on their CloudLinux servers.

I see in the docs that if I compile with the makefile, I can disable pam. This would be simple. But ... What will I miss if pam is disabled ? I'm building an application with users, passwords, accounts, sessions ... but all of this is of course handled with Erlang/PHP, my guess is that it will not change anything.

So are there any tisks disabling pam ?

Pam is there for you to use for http auth. If you're not using it but are instead using something else, then just run configure with --disable-pam, then run make. But you said you're using rebar, so the configure/make approach is inconvenient. I just pushed to master a change that lets you disable pam with rebar by setting the YAWS_DISABLE_PAM os environment variable, for example:

$ YAWS_DISABLE_PAM=1 rebar compile