Blog
mod_perl
I have several domains that I want to use. One of them is this site – but it just hosts a blog and various things under the hood that enable me to play with things. There is one domain that I actually want to use in order for me to do this I have to setup the infra-structure right.
I want it to use mod_perl and not the usual cgi way. One it is faster than cgi, two it allows me to have full control over all the phases of the request cycle and three I want to I worked in a rather large internet shop that ran on mod_perl for a time it was Europe’s biggest DVD store. Even then with only four wee servers doing its business it ran without any trouble at all! Now I don’t think my new venture will need the power of mod_perl but its best to start out with the best intentions!
I installed mod_perl back when I first got this server, so all I had to do was tell apache to do its thang. I will build my own handler in time, this was just to get it working.
Then further down:PerlModule ModPerl::Registry PerlSwitches -T
Seemed to work – wrote a very quick test, thing that annoys me is that the docs still refer to send_http_header but its not needed and caused it to break. Took it out – all grand.<Directory /www/xxxxxxxx.com/www/> SetHandler perl-script PerlResponseHandler ModPerl::Registry </Directory>
While I was here I got to thinking about my problems earlier in the week with seeing website tracking. So far so good on the Google Analytics front. It is very comprehensive and does way more than I want it to – but I’ll continue on using it. Now and again I will want to tail the access logs just to see who was where and doing what. My access logs were full of guff from me being on the admin section of the blog and just bombing about. I don’t want to have to use visitors just for seeing what was happening on a given day so while I was doing the above I shoved in a few rules to my custom log. Namely that I don’t care about my two work ip’s or my home one and images, css and javascript files are of little interest to me as well. I called the rule no_log for obvious reasons then just appened them onto my custom_log parameter. Now I can easily tail or view the access logs.#!/usr/bin/perl use strict; use warnings; use Apache2::RequestUtil;my $r = Apache2::RequestUtil->request;$r->content_type("text/html");$r->print("mod_perl rules!");
Now to set up capistrano and a dev server for this site. I am not developing on live code as tempting as it is for a sole project. Its best to start of this way even though it is a pain The real question is will I adpot my test first policy… DoubtfulSetEnvIf Remote_Host 82.68.249.126 no_log SetEnvIf Remote_Host 93.97.246.200 no_log SetEnvIf Remote_Host 80.76.195.116 no_log SetEnvIf Request_URI .gif no_log SetEnvIf Request_URI .jpg no_log SetEnvIf Request_URI .png no_log SetEnvIf Request_URI .js no_log
- Server (14)