acctually i don't really understand what i do here while setting up this route. it just use the example.. but you might be right and i can just use the get '/foo' => syntax instead if the my $route = app->routes->bridge(..)->to

something with flash seems to be broken here. i can use it on the one redirect but not on the other. it seems to be always empty after the redirect. but when i reload the page manually, the flash message shows up..

Kewl Idea on the new banner sri. My first impressions are good. I like the colors and "happiness" that is conveyed in the picture. My only comet is that "the web in a box" gives an idea of what you are looking at, right away. "web development can be fun again" is more ambiguous. ie, am I looking at a graphics program, etc, etc.. But overall,I really like the colors.

My first impression of the "trees" was that they are growing up to create a much larger ecosystem. Just like Mojolicous will do with web development. And the Unicorn rocks baby! For me it symbolizes the fact that Perl "is not supposed to exist any more" and therefore Mojolicous is the Unicorn. The big Prize!! :)

Where is an appropriate place to tell Mojolicious about the "url base" (not sure what the appropriate terminology might be) for a given application? I have apache doing rewrites on incoming requests to the cgi app but I'm not sure how to get Mojo to create urls that are appropriate (given the rewriting).

Hrmm, lemme look around. I hadn't considered I might be doing the rewriting poorly. The current rule i have takes request for (assuming no file on the system is found) my-app/some/path => my-app/app.cgi/some/path. This comes from an older, CGI::A which used a hook to cleanup the PATH_INFO env.

I disagree, I think it's a good point to start, I wanted to see what it would tell me. And I'm quite pleased. no garbage in the log output, nice output on error!, stacktrace if wanted but not in your face... hmmm yes, I'd say I like the error handling side very well!

thing is, I've written (haven't we all) my own duct-tape-for-the-web, I was quite happy to discover it was PSGI compatible and now it seems Mojo+Mustache is almost exactly what I have coded up myself. Glad to see all these idea's are converging. I'm leaving behing custom (mod_perl2) code to migrate to less code in PSGI mode, am now looking in adopting some Mojo :-)