Hi again,

I just uploaded a working example of the musician app:
http://github.com/davide/erlyweb/tree/50923c6cbe858b40e185719781c8ffb7cae1a7c0/examples/musician
I didn't use erlyweb:create_app/.. I simply converted the code from a
package-based version I had laying around.

I tested with my erlyweb code (same repository), so if you have any issues
you might want to check for differences with the official (=yariv's) branch.

Cheers,
:Davide

On Sat, May 23, 2009 at 3:13 PM, Steve Vinoski <[email protected]> wrote:

>
> On 5/23/09, Davide Marquês <[email protected]> wrote:
> > 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?
>
> Knowing what I know about the internals of yaws, I'd be very surprised
> if this made a difference. The parser for appmods looks for a list of
> sets of '<' PathElem, AppMod '>' tokens, one after another, just as
> Carl wrote in his conf file. As I just mentioned on this same issue
> over in erlang-questions, I just verified via tracing that this parser
> works correctly with multiple appmods on the same line.
>
> I'm using the very latest from github, of course, so perhaps the
> problem above was an issue in the past, but if so, it isn't anymore.
>
> --steve
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to