Hi!
I haven't used erlyweb in a while but I remember having no issues with
appmods.
The way I normally setup multiple appmods is using a new line for each
appmod, like so:
appmods = <"/yaws_showarg", yaws_showarg>
appmods = <"/noe", erlyweb>
Could you see if that solves the issue you're encountering?
Cheers,
:Davide
On Sat, May 23, 2009 at 2:54 PM, Carl <[email protected]> wrote:
>
> An by multiple users while going through the tutorial that is on
> Yariv's (the erlyweb
> creator) website. My yaws.conf looks like this:
>
> <server localhost>
> port = 8080
> listen = 0.0.0.0
> docroot = "C:\erlang\lib\Yaws-1.81/www"
> "C:/erlang/lib/Yaws-1.81/applications/music/www"
> appmods = <cgi-bin, yaws_appmod_cgi> <"/music", erlyweb>
>
> <opaque>
> appname = "music"
> </opaque>
> </server>
>
> The problems is that in the above appmod music is not found and
> errors. Surfing to http://localhost:8080/music produces an appmod
> error.
>
> But if you change the configuration so that the appmod music is the
> only one and under http://localhost:8080 then the config below works:
>
> <server localhost>
> port = 8080
> listen = 0.0.0.0
> docroot = "C:\erlang\lib\Yaws-1.81/www"
> "C:/erlang/lib/Yaws-1.81/applications/music/www"
> appmods = <"music", erlyweb>
>
> <opaque>
> appname = "music"
> </opaque>
> </server>
>
> This configuration pretty much means Erlyweb app has taken over this
> server instance (sigh just way too much like Rails). But according to
> Yaws docs and Yariv's blog this should not happen. So there is some
> conflict with Yaws or a problem with Erlyweb.
>
> /Carl
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"erlyweb" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/erlyweb?hl=en
-~----------~----~----~----~------~----~------~--~---
