I posted the other day that I couldn’t get Bugzilla working due to missing Perl modules*. Well last night I badgered 1and1.co.uk to install the modules, but I got a vauge no. I carefully read various pages, and got it installed… here’s how:
Read these instructions** first. If the CPAN shell complains about not having permissions to modify /root/.cpan, read this. Instead of putting the whole Apache httpd.conf <Directory> section (you probably dont have access to an httpd.conf…), you can put the AddHandler/Options/DirectoryIndex lines in a .htaccess file in the Bugzilla directory. Just to note that I couldn’t add the AllowOverride option in for some reason – it threw a 500 error…
Another thing that confused me was this:
perl -pi -e 's@use strict\;@use strict\; use lib \"/home/foo/perl/lib\"\;@' *cgi *pl Bug.pm processmail syncshadowdb
Perhaps the document is out of date, but none of those files existed. I changed Bugzilla.pm (note: you must use the FULL path to your local Perl installation, not just ~/myperl/lib!!!), and hey presto, it works! I now have a nice neat and tidy Bugzilla installation.
* It turns out that Bugzilla 3.2 (in release candidate stage) has a script to do all this for you – doh!
** Updated documentation link to the correct version – doh!
I signed up to Fire Eagle a couple of weeks ago, but have not used it since. I’m really not sure wether I should or not. It’s a cool idea being able to put on my blog where I am in the world, but on the other hand, it’s a bit of a risk… I might wait out the weaning period for it and see what the general public reaction is.
Bit of a funny name as well…
I was planning to write a WP plugin as the ones I’ve found so far have been rubbish, but I might wait it out until I actually start using it (if at all…)
I was searching today for a suitable Forge today for the projects I work on. Ideally I was looking for something like Sourceforge, but something that didn’t run in a VM, and didn’t require any back-end stuff. Source control isn’t required, just something I can put releases on. This ruled out a lot of typical forges I could’ve used (SFEE, gForge etc.). I asked Kelvin and he suggested a few, including Eventum and Flyspray. I have settled on Flyspray for now, we will see how it fares…
Edit: Well, I tried Flyspray and Eventum this evening, and didn’t really like either. I resolved myself to just using a bug tracking system, so I downloaded Bugzilla. That didn’t work due to some missing Perl bits, so I settled on phpBugTracker, the PHP alternative to that. So far, liking it! 
SOAP in PHP is quite simple, and as it’s something I’m doing at work at the moment, I thought I’d copy a bit of code to remind myself how to do it. Also to remind myself about the idea Chris had for Private Passwords.
Creating the client:
// WSDL client
$client = new SoapClient($wsdl);
// Non-WSDL client
$client = new SoapClient(NULL, array(
"location" => $endpoint_url . $script_name,
"uri" => $endpoint_url);
It’s that easy to create the client, and just as easy to make the request itself:
// WSDL client
$result = $client->doSomething("argument");
// Non-WSDL client
$result = $client->__soapCall("doSomething", array("argument"));As this is PHP, and PHP is lovely, the result is an object, and can be accessed as a normal object.
I’ve started a decent amount of work on a new secret website I’m developing together with Tom. I’ll be using Amazon Web Services for a large part of the site, so I thought I’d post my experiences so far.
For the most of the part, its really simple, and using cURL (or a simpler file_get_contents) makes it work pretty well. All you gotta do is formulate a nice-looking URL, retrieve it, and parse the results using something easy like simplexml_load_string.
Read the rest of this entry »
