I just run a happstack server on an alternative port, and then use mod_proxy to forward requests to the alternative port.<div><br></div><div>For example, <a href="http://happstack.com">happstack.com</a> is hosted at:</div>
<div><br></div><div><a href="http://src.seereason.com:9021/">http://src.seereason.com:9021/</a></div><div><br></div><div>but apache on that machine has a <a href="http://happstack.com">happstack.com</a> config that looks like:</div>
<div><br></div><div>------------</div><div><div><VirtualHost *:80></div><div> ServerAdmin <a href="mailto:user@example.org">user@example.org</a></div><div> ServerName <a href="http://www.happstack.com">www.happstack.com</a></div>
<div> ServerAlias <a href="http://happstack.com">happstack.com</a></div><div><br></div><div> ErrorLog /var/log/apache2/<a href="http://happstack.com/error.log">happstack.com/error.log</a></div><div> CustomLog /var/log/apache2/<a href="http://happstack.com/access.log">happstack.com/access.log</a> combined</div>
<div><br></div><div> ProxyRequests Off</div><div><span class="Apple-tab-span" style="white-space:pre"> </span> </div><div> <Proxy *></div><div> AddDefaultCharset off</div><div> Order deny,allow</div>
<div> <span class="Apple-tab-span" style="white-space:pre"> </span> Deny from all</div><div> </Proxy> </div><div><br></div><div> <Proxy <a href="http://127.0.0.1:9021/*">http://127.0.0.1:9021/*</a>></div>
<div> AddDefaultCharset off</div><div> Order deny,allow</div><div><span class="Apple-tab-span" style="white-space:pre"> </span> Allow from all</div><div> </Proxy></div><div><br>
</div><div> ProxyPass / <a href="http://127.0.0.1:9021/">http://127.0.0.1:9021/</a></div><div> ProxyPassReverse / <a href="http://127.0.0.1:9021/">http://127.0.0.1:9021/</a></div><div></VirtualHost></div><div>
---------</div><div><br></div><div>So users can just visit <a href="http://happstack.com/">http://happstack.com/</a></div><div><br></div><div>Hopefully I have not done something horribly insecure (easy to do with apache), but I believe this is correct.</div>
<div><br></div><div>- jeremy</div><div><br></div><br><div class="gmail_quote">On Sun, Feb 28, 2010 at 10:57 AM, brad clawsie <span dir="ltr"><<a href="mailto:clawsie@fastmail.fm">clawsie@fastmail.fm</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">-----BEGIN PGP SIGNED MESSAGE-----<br>
Hash: SHA1<br>
<br>
<br>
hi<br>
<br>
i'm currently doing some work on a personal site and was considering<br>
giving a haskell web tool a spin. i have a fairly complex apache<br>
configuration, so i don't want to try to replace it with a native<br>
haskell server, but instead use haskell via an interface to apache<br>
(i.e. something like wsgi, plack, etc).<br>
<br>
some searching shows hyena and yesod in various states of development,<br>
but i can't figure out if they are appropriate or ready for use. anyone have<br>
experiences using haskell behind apache? should i just try out something<br>
based on fastcgi? any anecdotes welcome<br>
<br>
thanks<br>
brad<br>
-----BEGIN PGP SIGNATURE-----<br>
Version: GnuPG v1.4.10 (FreeBSD)<br>
<br>
iEYEARECAAYFAkuKoJEACgkQxRg3RkRK91PVJwCdFD4dS47KjJuMcNVZmPkYXKyU<br>
ItsAnRoYBE39XtXyXDluh+pHSxzP+Qcd<br>
=91Ql<br>
-----END PGP SIGNATURE-----<br>
<div><div></div><div class="h5">_______________________________________________<br>
Haskell-Cafe mailing list<br>
<a href="mailto:Haskell-Cafe@haskell.org">Haskell-Cafe@haskell.org</a><br>
<a href="http://www.haskell.org/mailman/listinfo/haskell-cafe" target="_blank">http://www.haskell.org/mailman/listinfo/haskell-cafe</a><br>
</div></div></blockquote></div><br></div>