Not one to hang around, I decided to give Gregarius a whirl instead of just talking about it. You can find it at http://lakelandedge.co.uk/rss/.
Install was pretty simple as expected, but there were a few gotchas specific to my (and possibly others) configuration as I’m running LightTPD with FastCGI, so I’ll cover them here:
To save solving these yourself, here are some tailored instructions…
Tailored Install Instructions
php.ini, so that cgi.fix_pathinfo is 1 Now you can browse to you installation Before proceeding any further, go to the http://example.com/rss/admin/index.php?domain=config (changing the domain & path to suit obviously) and toggle rss.output.usemodrewrite to off Start using it!At some point, I may figure out the conversion of the rewrite rules to suit lighttpd, but at the moment I’m not to bothered as I prefer the un-rewritten URLs.
robots.txt
I prefered not to have my installation indexed (whilst googling for tips, I encountered lots of links pointing to feeds within Gregarius installations – very annoying), so I modified my robots.txt accordingly.
Authentication
I went with htdigest protection, but I sure you can figure out how to use basic.
htdigest from my previous Apache installation Add the following lines to your lighttpd.conf (in the relevant domain section if you’re hosting multiple sites:
auth.backend = “htdigest”
auth.backend.htdigest.userfile = ”/path/to/digest_file”
auth.require = ( ”/rss/admin/” =>
(
“method” => “digest”,
“realm” => “Gregarius”,
“require” => “valid-user”
)
)
Reload lighttpd and check everything is as expected.
Nice work. Well Gregarius only supports apache officially, but it has been known to work even on IIS.(ugh)
Just a couple of quick points.
* modrewrite will be turned off by default in the next released
* you will need to move your robots.txt file into your root directory for it to be effective. Editing the rss.config.robots option usually works better.
Ah, thanks for that - it answered a question I had about lighttpd authentication. I’ve been experimenting a bit with it myself, both as a back end for Rails applications (where it’s very, very fast) and for use with <a href="http://www.edgewall.com/trac/" rel="nofollow">Trac</a> as part of my multi-pronged approach to persuading a bunch of developers that no, they really DO want to migrate their source repositories from CVS to Subversion.