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