Installing MojoMojo2

The recommended way install is to follow the GitHub installation steps, so that all MojoMojo files end up in one directory, and you have the latest developer version. If you want to use a release version, after git clone, you can list the tags with git tag, and then checkout a specific tag: git checkout <tag_name>.


System Requirements

  • root privileges. Otherwise, you can still install MojoMojo using local::lib.
  • Perl 5.8+ and Catalyst 5.7+
  • database: in theory, any database back-end supported by DBIx::Class. MojoMojo has been cavite housing successfully tested with SQLite, PostgreSQL and MySQL.
  • memory requirements: on Linux, 60Mb per FastCGI process, regardless of the wiki database size or back-end type

External library dependencies

MYAPP_CONFIG is also a Catalyst-style environment variable name.

Here is an older example installation progress.

Installing the latest build from GitHub, step-by-step

This set of instructions will install MojoMojo's latest build from GitHub, assuming you know nothing about Catalyst or git. MojoMojo will run from the current directory using its built-in standalone web server.

Note: The following instructions assume the root user on a current Ubuntu system.

sudo su
aptitude install libxml2 libpng-dev libgif-dev libjpeg-dev expat libexpat1-dev
aptitude install libxslt1-dev libgdbm-dev docbook-xsl docbook-xsl-doc-html make
aptitude install libcatalyst-perl libcatalyst-modules-perl libcatalyst-modules-extra-perl 
aptitude install libdbix-class-datetime-epoch-perl libhtml-formfu-model-dbic-perl
aptitude install git-arch
git clone git://
# optional: git tag ; git checkout <release tag from the 'git tag' list>
cd mojomojo
cpan -i Module::Install
perl Makefile.PL
make test
# change mojomojo.conf if necessary
script/  # creates database
script/    # launch development server

For an example of installing the latest build from GitHub on openSuSE 11.2, see Installing on openSuSE.


In general, upgrading via CPAN (or your equivalent distribution package) should be the only step required to upgrade your MojoMojo installation:

$ sudo cpan
cpan[1]> install MojoMojo                                                                         
Running install for module 'MojoMojo'
Running make for M/MR/MRAMBERG/MojoMojo-1.00.tar.gz
Running make test
t/01app.t ....................... ok   
t/02pod.t ....................... ok     
t/03podcoverage.t ............... skipped: set TEST_POD to enable this test
t/04context.t ................... ok   


All tests successful.
Files=54, Tests=624, 165 wallclock secs ( 0.20 usr  0.11 sys + 99.55 cusr  5.01 csys = 104.87 CPU)
Result: PASS
  /usr/bin/make test -- OK
Running make install
Prepending /home/justin/.cpan/build/MojoMojo-1.00-hLVXEf/blib/arch /home/justin/.cpan/build/MojoMojo-1.00-hLVXEf/blib/lib to PERL5LIB for 'install'
Installing /usr/local/share/perl/5.10.0/
Installing /usr/local/share/perl/5.10.0/MojoMojo/mojomojo.conf


Installing /usr/local/bin/
Installing /usr/local/bin/
Installing /usr/local/bin/
Installing /usr/local/bin/
Installing /usr/local/bin/
Appending installation info to /usr/lib/perl/5.10/perllocal.pod
  /usr/bin/make install  -- OK

If you come from a pre-1.00 version to 1.00, please check mojomojo.conf for updates to the database connection info. The section should look like this:


    # DB User
    user              db_user
    password          db_password

    # SQLite DSN (default database type, recommended for small to medium deployments)
    dsn               dbi:SQLite:mojomojo.db



Other than that, there are no database schema changes planned as of yet, and a cpan MojoMojo (or git pull) should take care of upgrading.


Before starting the server, especially if you installed from GitHub, you may want to remove plugins that your installation won't use. To remove a plugin, just delete or move away its .pm file and associated directories from /lib/MojoMojo/Formatter.

The most common plugins you probably don't need are:

Resep Masakan Tutorial Blog Kata Mutiara Berita Terbaru Cepplux Blog Berita Terbaru Blog Kumpulan Cara Cerita 17 Tahun Cerita Dewasa Gambar Wallpaper Hip Replacement Recall Hip Repalcement Lawsuit

After installation

From here on, see Deployment. If you run into problems, see Troubleshooting.


TODO: document where files end up after installation. (alternatively, run updatedb and locate

My tags:
Popular tags:
Powered by Catalyst