Ushahidi under Ubuntu 9.10
Install essentials after build -
sudo aptitude install openssh-server vim
At this point I copy my pub key over so I can quit hassling with passwords.
scp .ssh/id_dsa.pub servername:
On the server:
- mkdir .ssh
- chmod 700 .ssh
- cat id_dsa.pub > .ssh/authorized_keys
- chmod 600 .ssh/authorized_keys
Log out and log back in again to test passwordless-ness 
of it.
Returning to software install,
* sudo aptitude install apache2-mpm-prefork libapache2-mod-php5, php5, php5-mcrypt, php5-mysql, php5-curl
I then copied my Ushahidi files over and unpacked.
* scp ushahidi.tgz servername:
On the server:
cd /var/www
sudo tar xzvf /home/<user>/ushahidi.tgz
Create your vhost:
I can't mention the path to apache2 without triggering the web application firewall. I am not complaining, just letting you know why this is vague.
I keep the default in place with just the server root and then add a vhost file in sites-available. Hope that makes sense. From the Apache2 ServerRoot:
sudo vi sites-available/vhosts
<VirtualHost ip-addr-here:80>DocumentRoot /var/www/ushahidi/ServerName fqdn.here.comServerAlias www.fqdn.here.comRewriteEngine OnRewriteOptions inheritErrorLog /var/log/apache2/error.logCustomLog /var/log/apache2/access.log combined</VirtualHost>
Write the file out and execute:
* sudo a2enmod rewrite
* sudo a2ensite vhost
* sudo apache2ctl restart
Install database software
* aptitude install mysql-server mysql-client
Create database and user
* mysql -u root -p ## (Note: on installing mysql-server you should have been prompted to create a new root password)
* mysql> CREATE DATABASE database1;
* mysql> GRANT ALL PRIVILEGES ON database1.* TO 'db-user'@'localhost' IDENTIFIED BY 'db-user-passwd';
* mysql> \q
Locally I have name service configured on my network, so after adding the hostname to DNS I accessed;
http://fqdn.here.com/installer
(If one is just messing about you can hack your host file, even under winders… C:\Windows\System32\Drivers\etc\hosts)
I then choose the Basic Install option and entered the new database info. That was it.
I could then access the administration interface with:
Logging in with u: admin p: admin, it's recommended that this u/p combo be changed as soon as possible.
Hope this is helpful.
<Worked for Me but Mileage May Vary Disclaimer>