Chapter 1. Midgard Installation Guide

Table of Contents
1.1. Minimum System and Software Requirements
1.2. Document Conventions
1.3. Installation Overview
1.4. Apache Installation
1.5. MySQL Installation
1.6. Glib Installation
1.7. Expat-lib Installation
1.8. Midgard Libraries (midgard-lib-1.4 Installation)
1.9. Midgard Database Installation
1.10. Midgard Apache Module
1.11. Midgard-php3 Installation
1.12. Midgard-php4 Installation
1.13. Apache Configuration File Edit
1.14. Updating the Midgard Database
1.15. Getting Started

The following is a modified version of the Installation Guide written by Eddie Azman for Midgard-1.1.1. It describes steps taken to install Midgard a number of times on a test server. Many a newbie to Midgard benifitted greatly from the original Eddie Azman document, the helpful assistance of the Midgard Community and the incredible insight and patience of Emiliano Heyns.

Here is a note on the test system used to develop these installation instructions for Midgard-1.4. This is mainly to illustrate that Midgard will run on fairly modest hardware (although how it holds up in a production environment will depend more on net traffic and available RAM).

We chose to install all the required components from source files because it provides the facility to fine tune the installation. If you choose to install some of the components differently (from binaries or rpm), your mileage will likely vary. You will have to verify that you have the development libraries for the various packages (Apache, Glib and MySQL).

1.1. Minimum System and Software Requirements

Midgard installation and operation depends on a number of packages and the installation will fail if those packages are not properly installed on your system. If these packages have been previously installed on your system, you can simply skip the sections detailing their installation.

If you're installing from binary packages for your platform, you'll most likely need the header files and other development-related material separately (sometimes found in a corresponding -dev or -devel package).