self.machine

Comments inside comments ! That seems to be a basic issue in PHP. Lets say i am including a php file, and i comment it out using /* */ and it super freaks out when that file has comments. Simple things that can save developer pain and i am sure it is not a difficult patch

So got to setting up OTRS, neat email based support system and it works pretty well it seems. There are some issues setting it up initially, but it integrates very well into your support email ! Should have thought of using it for kwippy once i think about it he he.

Just managed to get PHP compiled from source with php-fpm patch on it, the configure string was as follows

./configure –enable-fastcgi –enable-fpm –with-mcrypt –with-zlib –enable-mbstring –disable-pdo –with-pgsql –with-curl –disable-debug –with-pic –disable-rpath –enable-inline-optimization –with-bz2 –with-libxml-dir –with-zlib –enable-sockets –enable-sysvsem –enable-sysvshm –enable-pcntl –enable-mbregex –with-mhash –with-xsl –enable-zip –with-pcre-regex –with-mysql –with-gd –with-mysqli –with-jpeg-dir –with-freetype-dir –with-png-dir –with-pdflib

Though on debian getting GD with JPEG requires the open jpeg library [not the other jpeg lib]. Thats after going through the compilation a couple of time !

Also planning to move my server to a better setup, running out of memory right now.

Easiest way to get php with good looking urls running on your site . Works for drupal, wordpress and joomla.

server {
listen 80;
server_name www.domain.com;
index index.html index.htm index.php;
root /path/to/domain/files;
location / {
error_page 404 = //e/index.php?q=$uri;
}
location ~ .php$ {
include fastcgi_params;
fastcgi_pass 127.0.0.1:9000;
fastcgi_index index.php;
fastcgi_param SCRIPT_FILENAME /path/to/domain/files$fastcgi_script_name;
}
access_log /usr/local/nginx/logs/domain.access_log;
error_log /usr/local/nginx/logs/domain.error_log;
}