Part 2 The Database
Since without shell access we can’t use Horde’s setup (./scripts/setup.php) to do this for us we have to manually set up the database for Horde.

This step depends on your webhosters so i’ll just make it quick:
First create a database with your webhost, then find: hostname (often locahost), username, password, type (often tcp) and databasename for that database.

Now your webhoster probably offers some kind of management frontend (mostly phpmyadmin). There you navigate to your database and select the “SQL” tab.

In the editbox you will find there you have to paste some of the lines from the .sql file provided with Horde that matches your database. I use mysql so i used ./scripts/sql/create.mysql.sql.

Out host already created the database, the user etc. so we only need lines that create tables. In my file this would be lines 52 -> end (look for the first CREATE TABLE statement). Copy&Paste and press Submit. This should have given you no errors and created ~18 tables in your database.

In the next step we will create a basic configuration that allows Horde to run so we can do the rest of the setup from within it.

This experiment will most likely fail because i don’t have shell access and the php installation is probably missing vital modules .. but what else is there to do on a saturday evening

Part1: Horde is f***ing huge!


du -sch .
108M total


I’ll start by making horde a little slimer…
This will give me all the folders with locales other than german or english (cd to horde first)

find -iname ??_?? -type d | grep -v de_DE | grep -v en_US | grep -v en_GB

and this will delete them

find -iname ??_?? -type d | grep -v de_DE | grep -v en_US | grep -v en_GB | xargs rm -r


The same for the “.po” files:

find -iname ??_??.po -type f | grep -v de_DE | grep -v en_US | grep -v en_GB | xargs rm -r



du -sch .
51M total

Half the size, nice