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>.
On FreeBSD, install the p5-MojoMojo package. A Debian package for MojoMojo will soon be available.
TODO: document where files end up after installation.
install Catalyst. This can be as easy as
install the external libraries. For example on Ubuntu, run:
aptitude install libxml2 libpng-dev libgif-dev libjpeg-dev expat libexpat1-dev
On Windows, you can find
libxml2 and its dependencies at http://www.zlatkovic.com/pub/libxml/. You'll need
zlib1.dll in a directory listed in
To see how likely the installation tests are to succeed, check the CPAN Testers status of the MojoMojo dependencies.
As with any Catalyst application,
mojomojo_*.pl scripts will be installed installed in
configure MojoMojo. Usually, you'll want to add a local configuration file overriding values from mojomojo.conf. Since MojoMojo is a Catalyst application, it conforms to the naming convention for such configuration files and settings you add to
mojomojo_local.conf will override those in
mojomojo.conf (details at the Catalyst wiki - What is the precedence of various configuration setting locations?.
To point MojoMojo to an arbitrary configuration file, set
MYAPP_CONFIG is also a Catalyst-style environment variable name.
Here is an older example installation progress.
aptitude install libxml2 libpng-dev libgif-dev libjpeg-dev expat libexpat1-dev aptitude install libxslt1-dev libgdbm-dev docbook-xsl docbook-xsl-doc-html aptitude install git-arch git clone git://github.com/marcusramberg/mojomojo.git # optional: git tag ; git checkout <a release tag> cpan -i Module::Install cd mojomojo perl Makefile.PL make make test # change mojomojo.conf if necessary script/mojomojo_spawn_db.pl # creates database script/mojomojo_server.pl # launch development server
From here on, see Deployment. If you run into problems, see Troubleshooting.