- (e.g. `./bin/setup-site /org/packages.debian.org packages.debian.org')
-7) create a cache directory for the compiled templates, it needs to be writable by
- apache (i.e. on default etch by www-data). Default location is
- <topdir>/cache
-7) Include ./conf/apache.conf in apache's configuration, e.g. by symlinking it from
- /etc/apache2/sites-available/ and then using a2ensite
-8) Run ./bin/daily
-9) Setup ./bin/daily to be run regulary. In ./conf/crontab you can find an example crontab
- to do this. Actually preferable is to trigger the script by archive updates, but you
- will know best if and how to implement that in your setup.
+ (e.g. `./bin/setup-site /srv/packages.debian.org packages.debian.org')
+7) create a cache directory for the compiled templates, it needs to be writable
+ by apache (i.e. on default lenny by www-data). Default location is
+ <topdir>/cache. So
+ chown www-data <topdir>/cache
+ chmod 2770 <topdir>/cache
+8) Include ./conf/apache.conf in apache's configuration, e.g. by symlinking it
+ from /etc/apache2/sites-available/ and then using a2ensite
+9) Enable at least the following apache modules: `a2enmod expires rewrite'
+10) Run ./bin/daily
+ (this takes a while, especially the first time, as it downloads a lot of
+ data, [at the time of this writing approx. 900 MB], creates databases,
+ pre-builds heavy pages, etc.)
+11) Set up ./bin/daily to be run regulary. In ./conf/crontab you can find an
+ example crontab to do this. Actually preferable is to trigger the script by
+ archive updates, but you will know best if and how to implement that in your
+ setup.