Midgard Installation
From OpenPSA Wiki
The current Midgard generation is available in package form CentOS, Debian, Fedora, RHEL, openSUSE and xUbunutu distributions from the openSUSE Build System. For other distributions, source installation might be more advisable (Mac OS X installation is possible as well).
Source installation is partly automated and involves ./configure-ing, make-ing and make install-ing the Midgard Core, Apache 2 module, PHP language bindings and Midgard data, a package containing among others the MidCOM installation routines.
[edit] Setup
After the package installation, a MySQL-Database for Midgard can be created or updated via Datagard. MidCOM and the core MidCOM Components are installed with PEAR. The PEAR installation is triggered when creating a new database from Datagard, right after the Host creation.
Datagard usually creates everything required for a working Midgard database, i.e. an Apache vhost file, a DocumentRoot, Midgard configuration file, and directories for caches and Blobs. When Apache is correctly configured and restarted, Midgard should run and the new site can be created in the browser.
[edit] Troubleshooting
If the server is up responding to HTTP queries, but is serving from DocumentRoot instead of initializing Midgard, it is a good idea to check permissions, i.e. are the read/write privileges for the blob dir and the cache dir correctly set and is the midgard database user correctly configured in the Apache vhost configuration and in the midgard configuration file.
If that is is the case, check the server's, midgard's and midcom's log files to see if anything interesting comes up. Verify that the extensions for apache and PHP are loaded and verify that the entries in the databases host table are correct.
