Fedora Core

Supported Fedora Core releases
Installing Midgard with up2date
Installing Midgard with yum
Installing Midgard with apt
Upgrading Midgard on Fedora

Installing additional Midgard applications
Installing your own Midgard application
Listing available packages

Our Fedora Core repositories can be used with up2date, yum or apt. Choose your method below and follow the instructions. (For FC4, the yum method is the recommended one because up2date and apt aren't developed anymore. Oh, and please note that if you want to use midcom or aegir in FC4, read Using PHP 4.x in FC4 with yum below.)

Supported Fedora Core releases

Future (support planned) Fedora Core releases:

Fedora Core 4 (Stentz)
- Newest stable Midgard version: 1.7.6
  - midgard-framework is confirmed to be stable.
  - midgard-authentication (and therefore aegir too) has issues with PHP 5.x (thus not suitable for production with midgard-php4 compiled against PHP 5.x - you need to use PHP 4.x from FC3 and the midgard-php4-php4 package which is compiled against PHP 4.x).
  - midcom has issues with PHP 5.x (thus not suitable for production with midgard-php4 compiled against PHP 5.x - you need to use PHP 4.x from FC3 and the midgard-php4-php4 package which is compiled against PHP 4.x).
- Newest testing Midgard version: NA
- Newest unstable Midgard version: NA
- Using PHP 4.x in FC4 with yum
  - Add this line to your /etc/yum.conf: exclude=php-5.* php-*-5.*
  - Run yum remove php if you already have php installed
  - Install PHP 4.x from fedoralegacy.org FC3 updates repository (usually php, php-pear, php-gd and php-mbstring are needed)
  - Install Midgard as usual, but when you enter the install command, add midgard-php4-php4 to the package list; e.g. yum install midgard-php4-php4 midgard-cms

Old (support suspended) Fedora Core releases:

Fedora Core 3 (Heidelberg)
- Newest stable Midgard version: 1.7.6
- Newest testing Midgard version: NA
- Newest unstable Midgard version: NA
Fedora Core 2 (Tettnang)
- Newest stable Midgard version: 1.6.2
- Newest testing Midgard version: NA
- Newest unstable Midgard version: NA

Midgard is not working on Fedora when it has selinux enabled (default in FC3)! This is due to Apache HTTP Server selinux policy which doesn't allow httpd to write under the /var directory. In the mean time: If you have selinux disabled (default in FC2), Midgard works as usual. If you know how to fix this issue, please inform the Midgard developers on the Midgard IRC channel or send mail to the Midgard dev mailing list.

Installing Midgard with up2date

Import the GPG key.

For Fedora Core 4 (Stentz):

rpm --import http://www.puv.fi/download/midgard/fedora/4/i386/RPM-GPG-KEY

For Fedora Core 3 (Heidelberg):

rpm --import http://www.puv.fi/download/midgard/fedora/3/i386/RPM-GPG-KEY

For Fedora Core 2 (Tettnang):

rpm --import http://www.puv.fi/download/midgard/fedora/2/i386/RPM-GPG-KEY

Only for FC3 (FC4 has java provided): If you don't have Java RPM packages installed (MidCOM's default indexer backend requires Java), add this entry to the configuration file /etc/sysconfig/rhn/sources:

For Fedora Core 3 (Heidelberg):

yum sun-stable-fc3 http://www.puv.fi/download/sun/fedora/3/i386/RPMS.stable

Add this entry to the configuration file /etc/sysconfig/rhn/sources:

For Fedora Core 4 (Stentz):

yum midgard-stable-fc4 http://www.puv.fi/download/midgard/fedora/4/i386/RPMS.stable

For Fedora Core 3 (Heidelberg):

yum midgard-stable-fc3 http://www.puv.fi/download/midgard/fedora/3/i386/RPMS.stable

For Fedora Core 2 (Tettnang):

yum midgard-stable-fc2 http://www.puv.fi/download/midgard/fedora/2/i386/RPMS.stable

If you're going to install midcom-indexer-lucene (this package requires lucene from the jpackage-generic repository), set up up2date to use the generic free repository. Instructions: http://www.jpackage.org/repos.php

If you don't have MySQL server running at local or remote host, install and start it: up2date mysql-server && service mysqld start

Install Midgard 1.6.x with the command up2date midgard *. (You can update Midgard 1.6.x with the command up2date midgard.)

Install Midgard 1.7.x with the command up2date midgard-cms *. (You can update Midgard 1.7.x with the command up2date midgard-cms.)

Run datagard for setting up a new Midgard database and virtual host.

up2date is a great tool for automatic package updates, but it seems to work poorly when installing new packages. It may end up doing "Testing package set / solving RPM inter-dependencies..." for ages. Sometimes it works like a charm, but if you get this problem, install midgard with yum (follow the instructions) or download the RPMS and install them by hand running the command rpm -ivh _filename_ (filename can be an URL too) for each package (if you do this, please set the repository in your up2date sources anyway for getting updates in the future)

Installing Midgard with yum

Import the GPG key.

For Fedora Core 4 (Stentz):

rpm --import http://www.puv.fi/download/midgard/fedora/4/i386/RPM-GPG-KEY

For Fedora Core 3 (Heidelberg):

rpm --import http://www.puv.fi/download/midgard/fedora/3/i386/RPM-GPG-KEY

For Fedora Core 2 (Tettnang):

rpm --import http://www.puv.fi/download/midgard/fedora/2/i386/RPM-GPG-KEY

Configure yum repository sources.

For Fedora Core 4 (Stentz):

cd /etc/yum.repos.d  
wget http://www.puv.fi/download/midgard/fedora/4/i386/midgard-stable.repo

For Fedora Core 3 (Heidelberg):

cd /etc/yum.repos.d  
wget http://www.puv.fi/download/midgard/fedora/3/i386/midgard-stable.repo  
# If you don't have Java RPM packages installed (MidCOM's default indexer backend requires Java):  
wget    http://www.puv.fi/download/sun/fedora/3/i386/sun-stable.repo

For Fedora Core 2 (Tettnang), add these entries to the configuration file /etc/yum.conf:

[midgard-stable]
name=Midgard Project Fedora Compatible Packages (stable)  
baseurl=http://www.puv.fi/download/midgard/fedora/$releasever/i386/RPMS.stable  
gpgcheck=1

If you're going to install midcom-indexer-lucene (this package requires lucene from the jpackage-generic repository):

    cd /etc/yum.repos.d/ && wget http://www.jpackage.org/jpackage.repo

If you don't have MySQL server running at local or remote host, install and start it: yum install mysql-server && service mysqld start

Install Midgard 1.6.x with the command yum install midgard. (You can update Midgard 1.6.x with the command yum update midgard.)

Install Midgard 1.7.x with the command yum install midgard-cms. (You can update Midgard 1.7.x with the command yum upgrade midgard-cms.)

Run datagard for setting up a new Midgard database and virtual host.

Installing Midgard with apt

Import the GPG key.

For Fedora Core 4 (Stentz):

cd /etc/apt/gpg  
wget -O MIDGARD-RPM-GPG-KEY http://www.puv.fi/download/midgard/fedora/4/i386/RPM-GPG-KEY  
rpm --import MIDGARD-RPM-GPG-KEY

For Fedora Core 3 (Heidelberg):

cd /etc/apt/gpg  
wget -O MIDGARD-RPM-GPG-KEY http://www.puv.fi/download/midgard/fedora/3/i386/RPM-GPG-KEY  
rpm --import MIDGARD-RPM-GPG-KEY

For Fedora Core 2 (Tettnang):

cd /etc/apt/gpg  
wget -O MIDGARD-RPM-GPG-KEY http://www.puv.fi/download/midgard/fedora/2/i386/RPM-GPG-KEY  
rpm --import MIDGARD-RPM-GPG-KEY

Configure apt repository sources.

For Fedora Core 4 (Stentz):

cd /etc/apt/sources.list.d  
wget http://www.puv.fi/download/midgard/fedora/4/i386/midgard.list

For Fedora Core 3 (Heidelberg):

cd /etc/apt/sources.list.d  
wget http://www.puv.fi/download/midgard/fedora/3/i386/midgard.list  
# If you don't have Java RPM packages installed (MidCOM's     default indexer backend requires Java):  
wget http://www.puv.fi/download/sun/fedora/3/i386/sun.list

For Fedora Core 2 (Tettnang):

cd /etc/apt/sources.list.d  
wget http://www.puv.fi/download/midgard/fedora/2/i386/midgard.list

Run apt-get update midgard for updating the apt database (this adds our repository into your apt).

If you're going to install midcom-indexer-lucene (this package requires lucene from the jpackage-generic repository), set up apt to use the generic free repository. Instructions: http://www.jpackage.org/repos.php

If you don't have MySQL server running at local or remote host, install and start it: apt-get install mysql-server && service mysqld start

Install Midgard 1.6.x with the command apt-get install midgard. (You can update Midgard 1.6.x with the command apt-get update midgard && apt-get upgrade midgard.)

Install Midgard 1.7.x with the command apt-get install midgard-cms. (You can update Midgard 1.7.x with the command apt-get update midgard && apt-get dist-upgrade midgard-cms.)

Run datagard for setting up a new Midgard database and virtual host.

Upgrading Midgard on Fedora

If you are upgrading Midgard from 1.6 to 1.7, the easiest way to do this is to run full system update command (up2date -u, yum upgrade or apt-get update && apt-get dist-upgrade).

The Midgard CMS package is now named as midgard-cms. You have now all the control you need. Every Midgard application is now packaged as RPM and installed by RPM (no need to run Datagard for importing the package - RPM does this for you).

Installing additional Midgard applications

If you just want to use SpiderAdmin and nothing else, install the spider package (up2date spider, yum install spider or apt-get install spider).

Installing your own Midgard application

If you are a developer and want to test the development versions of the appications, install only the Midgard Framework package (called midgard-framework) and run the Datagard DB installation.

Then place your application (.tar* or .xml*) under /usr/share/midgard/pkgs/ and run datagard's import to install your own package.

Listing available packages

To see which packages are available, use the search functions available in the install tools (up2date --show-available | grep <pkgname>, yum search <pkgname> or apt-cache search <pkgname>) or browse the PUV FC3 repository:

If you are using other repository than stable, please note that you must enable also the stable repository (and testing if you are using unstable) to be able to have access to all available packages. The packages walk through the repository by entering unstable and exiting stable (older packages for the same major Midgard version are usually removed when a new bugfix release is published).

Do not use the unstable repository in production systems as it contains usually CVS snapshots or packages that were "just built". The testing repository is often a good choise as this enables newer versions like beta releases. But for serious production, please use the stable repository which contains the official stable Midgard release versions of the packages.