resistance is obsolete ™ ;-)

Installation Instructions

You will find installation instructions for on a per distribution basis. The OGo project provides specific packages for most of the common platforms:

Debian, Fedora, FreeBSD, Gentoo, MacOSX, Mandrake, RedHat, Slackware, SuSE, Conectiva, Ubuntu, Solaris, iSeries, Windows, Source

Heads Up! The recommended version for deployments is the latest OGo 1.0 beta release.

instant OGo Logo The installation of OGo is easy but not trivial for people new to GNU/Linux! If you don't already know how to configure Apache or PostgreSQL, consider to consult your local Linux guru, buy a SKYRiX distribution of OGo or try the instant OGo CD

Getting Help: If you have problems with the installation, please join one of the users mailinglists. You'll find help with configuring OGo and of course, with getting Apache and PostgreSQL up and running. Also make sure you check the mailinglist archives! Pasting an issue into Google often helps too.
A word of warning: do not use Google to search for installation instructions, a lot of deprecated documents are floating around on the web. Stick to what is provided in this section.

Short Intro: trunk vs releases

Since the move from CVS to Subversion, the OGo developers can easily provide alpha quality snapshots. Previously the OGo project only provided so called "nightly builds" which where generated from the very latest source changes of the developers (so called "CVS HEAD").

While those nightly builds provided a very good quality due to the maturity of the OGo sourcecode base, you could still run into "grape builds", builds which were broken due to recent changes.

So what was formerly provided by "nightly builds", the CVS HEAD, is now called "trunk" in Subversion terminology. If you fetch a trunk build, you get the very latest changes (including the very latest bugs).

This is where 'releases' come in. With Subversion its very easy to freeze a certain 'trunk' as a release. Note that a release can be of Alpha quality, that is, it got minimal testing. Yet a release is 'frozen' and it is ensured that the release isn't a "grape build".

Summary: use some release, unless you know what you are doing :-)

TODO: describe the process for stable/unstable branches.


We welcome your feedback!
This site is sponsored by
SKYRIX Software AG
ZideOne GmbH