Mojolicious::Guides::Cookbook - Cookbook


Cooking with Mojolicious, recipes for every taste.


Getting Mojolicious and Mojolicious::Lite applications running on different platforms.

Builtin Server

Mojolicious contains a very portable HTTP 1.1 compliant web server. It is usually used during development but is solid and fast enough for small to mid sized applications.

  % ./script/myapp daemon
  Server available at

It has many configuration options and is known to work on every platform Perl works on.

  % ./script/myapp help daemon
  ...List of available options...

Another huge advantage is that it supports TLS and WebSockets out of the box.

  % ./script/myapp daemon --listen https://*:3000
  Server available at

A development certificate for testing purposes is built right in, so it just works.


For bigger applications Mojolicious contains the UNIX optimized preforking web server Mojo::Server::Hypnotoad that will allow you to take advantage of multiple cpu cores and copy-on-write.

  |- Mojo::Server::Daemon [1]
  |- Mojo::Server::Daemon [2]
  |- Mojo::Server::Daemon [3]
  `- Mojo::Server::Daemon [4]

It is based on the normal builtin web server but optimized specifically for production environments out of the box.

  % hypnotoad script/myapp
  Server available at

Config files are plain Perl scripts for maximal customizability.

  # hypnotoad.conf
  {listen => ['http://*:80'], workers => 10};

But one of its biggest advantages is the support for effortless zero downtime software upgrades. That means you can upgrade Mojolicious, Perl or even system libraries at runtime without ever stopping the server or losing a single incoming connection, just by sending it a USR2 signal.

  % kill -s 'USR2' `cat`


One of the most popular setups these days is the builtin web server behind a Nginx reverse proxy.

  upstream myapp {
  server {
    listen 80;
    server_name localhost;
    location / {
      proxy_read_timeout 300;
      proxy_pass http://myapp;
      proxy_set_header Host $http_host;
      proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;

You might also want to enable reverse proxy support in hypnotoad. This allows Mojolicious to automatically pick up the X-Forwarded-For, X-Forwarded-Host and X-Forwarded-HTTPS headers.

  # hypnotoad.conf
  {proxy => 1};


CGI is supported out of the box and your Mojolicious application will automatically detect that it is executed as a CGI script.

  ScriptAlias / /home/sri/myapp/script/myapp/


FastCGI is also supported out of the box and your Mojolicious application will automatically detect that it is executed as a FastCGI script.

  FastCgiIpcDir /home/sri/myapp
  FastCgiServer /home/sri/myapp/script/myapp -processes 1
  Alias / /home/sri/myapp/script/myapp/


PSGI is an interface between Perl web frameworks and web servers, and Plack is a Perl module and toolkit that contains PSGI middleware, helpers and adapters to web servers. PSGI and Plack are inspired by Python's WSGI and Ruby's Rack. Mojolicious applications are ridiculously simple to deploy with Plack.

  % plackup ./script/myapp
  HTTP::Server::PSGI: Accepting connections at http://0:5000/

Plack provides many server and protocol adapters for you to choose from such as FCGI, SCGI and mod_perl. Make sure to run plackup from your applications home directory, otherwise libraries might not be found.

  % plackup ./script/myapp -s FCGI -l /tmp/myapp.sock

Because plackup uses a weird trick to load your script, Mojolicious is not always able to detect the applications home directory, if thats the case you can simply use the MOJO_HOME environment variable. Also note that app->start needs to be the last Perl statement in the application script for the same reason.

  % MOJO_HOME=/home/sri/myapp plackup ./script/myapp
  HTTP::Server::PSGI: Accepting connections at http://0:5000/

Some server adapters might ask for a .psgi file, if thats the case you can just point them at your application script because it will automatically act like one if it detects the presence of a PLACK_ENV environment variable.

Apache/mod_perl (PSGI/Plack)

mod_perl is a good example for a PSGI adapter that is used without plackup, note that setting the PLACK_ENV environment variable is required for Mojolicious PSGI detection.

  <VirtualHost *:80>
    ServerName localhost
    DocumentRoot /home/sri/myapp/public

      $ENV{PLACK_ENV} = 'production';
      $ENV{MOJO_HOME} = '/home/sri/myapp';

    <Location /myapp>
      SetHandler perl-script
      PerlHandler Plack::Handler::Apache2
      PerlSetVar psgi_app /home/sri/myapp/script/myapp


Sometimes you might have to deploy your application in a blackbox environment where you can't just change the server configuration or behind a reverse proxy that passes along additional information with X-* headers. In such cases you can use a before_dispatch hook to rewrite incoming requests.

  app->hook(before_dispatch => sub {
    my $self = shift;
      if $self->req->headers->header('X-Forwarded-Protocol') eq 'https';


You can also use the builtin web server to embed Mojolicious applications into alien environments like foreign event loops.

  use Mojolicious::Lite;
  use Mojo::Server::Daemon;

  # Normal action
  get '/' => sub {
    my $self = shift;
    $self->render(text => 'Hello World!');

  # Connect application with custom daemon
  my $daemon =
    Mojo::Server::Daemon->new(app => app, listen => ['http://*:8080']);

  # Call "one_tick" repeatedly from the alien environment
  $daemon->ioloop->one_tick while 1;


When we say Mojolicious is a web framework we actually mean it.

Web Scraping

Scraping information from web sites has never been this much fun before. The built in XML/HTML5 parser Mojo::DOM supports all CSS3 selectors that make sense for a standalone parser.

  # Fetch web site
  my $ua = Mojo::UserAgent->new;
  my $tx = $ua->get('');

  # Extract title
  print 'Title: ', $tx->res->dom->at('head > title')->text, "\n";

  # Extract headers
  $tx->res->dom('h1, h2, h3')->each(sub {
    print 'Header: ', shift->all_text, "\n";

Especially for unit testing your Mojolicious applications this can be a very powerful tool.

JSON Web Services

Most web services these days are based on the JSON data-interchange format. That's why Mojolicious comes with the possibly fastest pure-Perl implementation Mojo::JSON built right in.

  # Fresh user agent
  my $ua = Mojo::UserAgent->new;

  # Fetch the latest news about Mojolicious from Twitter
  my $search = '';
  for $tweet (@{$ua->get($search)->res->json->{results}}) {

    # Tweet text
    my $text = $tweet->{text};

    # Twitter user
    my $user = $tweet->{from_user};

    # Show both
    my $result = "$text --$user\n\n";
    utf8::encode $result;
    print $result;

Basic Authentication

You can just add username and password to the URL.

  my $ua = Mojo::UserAgent->new;
  print $ua->get('')->res->body;

Decorating Followup Requests

Mojo::UserAgent can automatically follow redirects, the on_start callback allows you direct access to each transaction right after they have been initialized and before a connection gets associated with them.

  # User agent following up to 10 redirects
  my $ua = Mojo::UserAgent->new(max_redirects => 10);

  # Add a witty header to every request
  $ua->on_start(sub {
    my $tx = pop;
    $tx->req->headers->header('X-Bender' => 'Bite my shiny metal ass!');
    print 'Request: ', $tx->req->url->clone->to_abs, "\n";

  # Request that will most likely get redirected
  print 'Title: ',
    $ua->get('')->res->dom->at('head > title')->text, "\n";

This even works for proxy CONNECT requests.

Streaming Response

Receiving a streaming response can be really tricky in most HTTP clients, Mojo::UserAgent makes it actually easy.

  my $ua = Mojo::UserAgent->new;
  my $tx = $ua->build_tx(GET => '');
  $tx->res->body(sub { print $_[1] });

The body callback will be called for every chunk of data that is received, even chunked encoding will be handled transparently if necessary.

Streaming Request

Sending a streaming request is almost just as easy.

  my $ua      = Mojo::UserAgent->new;
  my $tx      = $ua->build_tx(GET => '');
  my $content = 'Hello world!';
  $tx->req->headers->content_length(length $content);
  my $drain;
  $drain = sub {
    my $req   = shift;
    my $chunk = substr $content, 0, 1, '';
    $drain    = undef unless length $content;
    $req->write($chunk, $drain);

The drain callback passed to write will be invoked whenever the entire previous chunk has been written to the kernel send buffer.

Large File Downloads

When downloading large files with Mojo::UserAgent you don't have to worry about memory usage at all, because it will automatically stream everything above 250KB into a temporary file.

  # Lets fetch the latest Mojolicious tarball
  my $ua = Mojo::UserAgent->new(max_redirects => 5);
  my $tx = $ua->get('');

To protect you from excessively large files there is also a global limit of 5MB by default, which you can tweak with the MOJO_MAX_MESSAGE_SIZE environment variable.

  # Increase limit to 1GB
  $ENV{MOJO_MAX_MESSAGE_SIZE} = 1073741824;

Large File Upload

Uploading a large file is even easier.

  # Upload file via POST and "multipart/form-data"
  my $ua = Mojo::UserAgent->new;
    {image => {file => '/Users/sri/hello.png'}});

And once again you don't have to worry about memory usage, all data will be streamed directly from the file.

  # Upload file via PUT
  my $ua     = Mojo::UserAgent->new;
  my $asset  = Mojo::Asset::File->new(path => '/Users/sri/hello.png');
  my $tx     = $ua->build_tx(PUT => '');


Mojo::UserAgent has been designed from the ground up to be non-blocking, the whole blocking API is just a simple convenience wrapper. Especially for high latency tasks like web crawling this can be extremely useful, because you can keep many parallel connections active at the same time.

  # FIFO queue
  my @urls = qw/;

  # User agent following up to 5 redirects
  my $ua = Mojo::UserAgent->new(max_redirects => 5);

  # Crawler
  my $crawl;
  $crawl = sub {
    my $id = shift;

    # Dequeue or wait for more URLs
    return Mojo::IOLoop->timer(2 => sub { $crawl->($id) })
      unless my $url = shift @urls;

    # Fetch non-blocking just by adding a callback
    $ua->get($url => sub {
      my $tx = pop;

      # Extract URLs
      print "[$id] $url\n";
      $tx->res->dom('a[href]')->each(sub {
        my $e = shift;

        # Build absolute URL
        my $url = Mojo::URL->new($e->attrs('href'))->to_abs($tx->req->url);
        print " -> $url\n";

        # Enqueue
        push @urls, $url;

      # Next

  # Start a bunch of parallel crawlers sharing the same user agent
  $crawl->($_) for 1 .. 3;

  # Start event loop

You can take full control of the Mojo::IOLoop event loop.

Command Line

Don't you hate checking huge HTML files from the command line? Thanks to the mojo get command that is about to change. You can just pick the parts that actually matter with the CSS3 selectors from Mojo::DOM.

  % mojo get 'head > title'

How about a list of all id attributes?

  % mojo get '*' attr id

Or the text content of all header tags?

  % mojo get 'h1, h2, h3' text

Maybe just the text of the third header?

  % mojo get 'h1, h2, h3' 3 text

You can also extract all text from nested child elements.

  % mojo get '#mojobar' all

The request can be customized as well.

  % mojo get --method post --content 'Hello!'
  % mojo get --header 'X-Bender: Bite my shiny metal ass!'

You can follow redirects and view the headers for all messages.

  % mojo get --redirect --verbose 'head > title'

This can be an invaluable tool for testing your applications.

  % ./ get /welcome 'head > title'


Fun hacks you might not use very often but that might come in handy some day.

Making Your Application Installable

Ever thought about releasing your Mojolicious application to CPAN? It's actually much easier than you might think.

  % mojo generate app
  % cd my_mojolicious_app
  % mv public lib/MyMojoliciousApp/
  % mv templates lib/MyMojoliciousApp/

The trick is to move the public and templates directories so they can get automatically installed with the modules.

  package MyMojoliciousApp;
  use Mojo::Base 'Mojolicious';

  use File::Basename 'dirname';
  use File::Spec;

  # Every CPAN module needs a version
  our $VERSION = '1.0';

  sub startup {
    my $self = shift;

    # Switch to installable home directory
      File::Spec->catdir(dirname(__FILE__), 'MyMojoliciousApp'));

    # Switch to installable "public" directory

    # Switch to installable "templates" directory


    my $r = $self->routes;


Thats really everything, now you can package your application like any other CPAN module.

  % ./script/my_mojolicious_app generate makefile
  % perl Makefile.PL
  % make test
  % make manifest
  % make dist

Hello World

If every byte matters this is the smallest Hello World application you can write with Mojolicious::Lite.

  use Mojolicious::Lite;
  any {text => 'Hello World!'};

It works because all routes without a pattern default to / and automatic rendering kicks in even if no actual code gets executed by the router. The renderer just picks up the text value from the stash and generates a response.

Hello World Oneliner

The Hello World example above can get even a little bit shorter in an ojo oneliner.

  perl -Mojo -e'a({text => "Hello World!"})->start' daemon

And you can use all the commands from Mojolicious::Commands.

  perl -Mojo -e'a({text => "Hello World!"})->start' get -v /

Keeping Mojolicious Up-To-Date

This tasty oneliner will keep your Mojolicious as fresh as possible.

  sudo sh -c "curl -L | perl -"

jQuery (Content Distribution Network)

These days Mojolicious ships with a bundled version of jQuery, which you can easily use as a fallback for applications that might be used offline from time to time.

  <%= javascript
    '' %>
  <%= javascript begin %>
    if (typeof jQuery == 'undefined') {
      var e = document.createElement('script');
      e.src = '/js/jquery.js';
      e.type = 'text/javascript';
  <% end %>


You can continue with Mojolicious::Guides now or take a look at the Mojolicious wiki, which contains a lot more documentation and examples by many different authors.