Yeah, I know - loadsa previous threads about mod_perl.
And I've spent a good part of today reading them, and the rackshack forums, and the apache docs ...
But I still have questions I haven't seen answers to, so before I take the plunge:
1) mod_perl is already installed on my server. After following the steps in the readme, do I have to tell LSQL to use mod_perl or does it just "know"?
2) I'm reading about installing a thin and a fat apache server on the one box. That might be technical overkill right now, but does that mean that a single mod_perl server is now deprecated? Is running a fairly large database/low hits dynamic LSQL installation under mod_perl likely to be better or worse on balance? It shares a fairly busy server and I'm looking at this as one of a number of load-reducing steps. In fact, the low hits thing isn't really relevant as the main problem occurs when the site gets hit hard by SE 'bots - so its the ability to keep loads down undre heavy traffic thats the issue.
3) Looking ahead, I'd like to be able to run more than one LSQL site on the same server. Technically (not licencing-wise) - could that be done under mod_perl and would it influence how I set up this first site? I'm probably only really concerned about page.cgi and search.cgi from a load POV. My suspicion is it can't be done - though maybe renaming these progs on a second installation and loading them into mod_perl would be an option?
TIA for any pointers.
[edited to add:]
oh yeah, 2 more qs:
4) the apache directives - they go in the main httpd.conf for the whole server, or in the confs for the specific virtual host/domain?
5) is there any danger that globals I have added could mess up under mod_perl - especially if they are , er, sloppy with regard to declaring variables etc ?
And I've spent a good part of today reading them, and the rackshack forums, and the apache docs ...
But I still have questions I haven't seen answers to, so before I take the plunge:
1) mod_perl is already installed on my server. After following the steps in the readme, do I have to tell LSQL to use mod_perl or does it just "know"?
2) I'm reading about installing a thin and a fat apache server on the one box. That might be technical overkill right now, but does that mean that a single mod_perl server is now deprecated? Is running a fairly large database/low hits dynamic LSQL installation under mod_perl likely to be better or worse on balance? It shares a fairly busy server and I'm looking at this as one of a number of load-reducing steps. In fact, the low hits thing isn't really relevant as the main problem occurs when the site gets hit hard by SE 'bots - so its the ability to keep loads down undre heavy traffic thats the issue.
3) Looking ahead, I'd like to be able to run more than one LSQL site on the same server. Technically (not licencing-wise) - could that be done under mod_perl and would it influence how I set up this first site? I'm probably only really concerned about page.cgi and search.cgi from a load POV. My suspicion is it can't be done - though maybe renaming these progs on a second installation and loading them into mod_perl would be an option?
TIA for any pointers.
[edited to add:]
oh yeah, 2 more qs:
4) the apache directives - they go in the main httpd.conf for the whole server, or in the confs for the specific virtual host/domain?
5) is there any danger that globals I have added could mess up under mod_perl - especially if they are , er, sloppy with regard to declaring variables etc ?