The Perl Toolchain Summit needs more sponsors. If your company depends on Perl, please support this very important event.

NAME

Mojolicious::Guides::FAQ - Frequently Asked Questions

OVERVIEW

This document contains the most frequently asked questions about Mojolicious together with the right answers.

QUESTIONS

Does Mojolicious run on Windows systems?

Sure it does! Right now there are two different ways of running Perl on the Windows platform. One is Strawberry Perl and the other is ActiveState Perl. Both are capable Perl distributions which are stable, mature and ready for production. But Strawberry Perl is quite a bit better at dealing with the CPAN and especially XS based modules due to its remarkable toolchain. With it you can even install modules straight from the source as you would do on a Unix based machine.

Is it possible to run the builtin webserver on Windows?

It is! The builtin webserver is great way to run your Mojolicious web application on any platform. See Mojolicious::Guides::Cookbook for more information about running and deploying Mojolicious applications.

Note that if you run your application with the --reload option Windows will lock your files. A simple Windows editor like WordPad will complain that the file has already been opened by a different proccess. More capable editors can handle this accordingly and force the change.

Whats the easiest way to install Mojolicious on UNIX?

Quite possibly this oneliner.

    sudo -s 'curl -L cpanmin.us | perl - "Mojolicious"'

I think Mojolicious is awesome, how can i support you guys?

Share your success story via blog or twitter, get more people hooked! :)

I think i have found a bug, what should i do now?

Prepare a test case demonstrating the bug, you are not expected to fix it yourself, but you'll have to make sure the developers can replicate your problem. Sending in your whole application generally does more harm than good, the t directory of this distribution has many good examples for how to do it right. Writing a test is usually the hardest part of fixing a bug, so the better your test case the faster it can be fixed. ;)

Once thats done you can contact the developers via GitHub (http://github.com/kraih/mojo), mailing list (http://groups.google.com/group/mojolicious) or IRC (#mojo on irc.perl.org).

If you decide to fix the bug yourself make sure to also take a look at Mojolicious::Guides::CodingGuidelines.