The setup was all very nice... Just note that it will not handle subdomains unless you hack it (you need to change about 10 lines of code).
But... I have a maximum script running time on my shared server, and don't want to use up my precious bandwidth either; I have to retrieve via http due to PHP scripts.
Anyway, I installed perlfect on my off-line development windows machine, and built up the DB. Both DB_File and Berkeley DB are the exact same version as on the production server (BSD box), but it tells me the database format is not compatible. I've given up on the idea of reinstalling DB_File and Berkeley DB on the production server, so I'm looking into alternatives.
Have any of you tackled such a problem? What would you recommend?
ht://Dig doesn't seem to rely on external DB libraries, so that might work, but the size of the index gets big very quickly!
Cheers,
Alex
More thinking, and ... I can only see two ways out of this, and neither are ideal solutions:
Hmmm...