Restarting Lighttpd for each change? Error logging?

[Erik Terpstra]

To answer my own question, it seems that the requirement to restart 
after each change is only the case for fast-cgi.
Also lighttpd behaves very unpredictable to me, so I am now using a 
Mongrel/Camping + Apache/ProxyReverse combination which seems to work 
much better.

Erik Terpstra wrote:
> Hi,
>
> It seems that for each change that I make in my camping application, I 
> have to restart lighttpd to make it work.
>
> Also whenever something goes wrong, a syntax error in my camping 
> application for example, things just stop working and I can't see any 
> error messages in the lighttpd logs or any other log.
>
> I just followed the instructions to use Camping with lighttpd on the wiki.
>
> Any ideas?
>
> Erik.
> _______________________________________________
> Camping-list mailing list
> Camping-list at rubyforge.org
> http://rubyforge.org/mailman/listinfo/camping-list
>
>