Re: [Erlyaws-list] running yaws on port 80

[<ca...@gm...>]

On 11/15/06, Bruce Fitzsimons <br...@fi...> wrote:

> Putting a proxy such as http://www.apsis.ch/pound/  in front may be what
> you want. stunnel works, but requires ongoing maintenance per server.

I hadn't heard of pound before, but will look into it, thanks.  Looks
like there's a Debian package for it too.

> The other option is to put apache on the front, and proxy the dynamic
> bits to yaws, which is what I (and many others) do -- there is so much
> built on top of apache that it is hard to justify my effort of getting
> standard php apps (for example) to work properly/quickly/reliably
> against yaws -- you can, but wouldn't you rather be writing your
> application in erlang?

Part of my motivation is to completely get rid of Apache.  It's large
and bloated, and even after using it for a decade, I barely understand
the complex configuration just enough to get it working. If you've
been following my messages on this list as of late, you'll see that I
have been trying to get standard php/cgi apps to work
properly/quickly/reliably under yaws by writing appmods and the like.
I've been successful at this.  So far I have Wordpress (php), Mailman,
and MoinMoin all working perfectly under yaws.  I feel confident that
more or less any app can be made to work under yaws with a bit of
erlang coding.  Or at least, those that I use on my sites.

> but it took me a while to recognise that I didn't
> want to be a trailblazer getting tested, stable, webapps (gallery for
> example) to work under yaws.

Haha, I guess that's exactly what I've being doing, probably to the
annoyance of Klacke and others on here.  :P

--=20
Cheers, L=E1szl=F3 (Yaws trailblazer)