Left Brain Things

I have used this script on my linux system without any issues. Do not use it on Windows.

Script is very simple, you can change it to recode from other encodings just by changing one line of code.

conveter.pl:

#!/usr/bin/perl -w
use strict;
use URI::Escape;

my @files;
while(my $file = <>) {
	chomp $file;
	push @files, $file;
}

foreach my $file (reverse @files) {
	if( $file =~ /%/ ) {
		print "$file\n";
		convert($file);
	}
}

sub convert {
	my $file = shift; # it can be directory
	die unless $file =~ /^(.*?)([^\/]+)$/;
	my $new_filename = "$1" . uri_unescape("$2");
	print "$new_filename\n";
	rename($file,$new_filename) or die;
}

Usage: Save it as “conveter.pl” to DokiWiki data/ directory, make it executable, then:

You can correct “PROT_EXEC|PROT_WRITE failed” error by disabling selinux restrains on Apache.
Or you can disable selinux completely if you know what you are doing.

Hello.
First of all you should have PHP and Nginx up and running.

After many tests this Nginx config works fine with Kalkun 0.7.1:

server {
        listen 80;
        server_name kalkun.domain.com;

	access_log /var/log/nginx/kalkun.access.log;
	error_log /var/log/nginx/kalkun.error.log;
		
	root /var/www/localhost/htdocs/kalkun;

        client_max_body_size 10G;
        fastcgi_buffers 8 16K;
	fastcgi_buffer_size 53k;

	location / {
		index  index.php;
	}

	location ~* ^.+.(jpg|jpeg|gif|css|png|js|ico|xml)$ {
		access_log        off;
		expires           360d;
	}

	location ~ /\.ht {
		deny  all;
	}

        # pass the PHP scripts to FastCGI server listening on 127.0.0.1:9000
        location ~ ^(.+?\.php)(/.*)?$ {
                try_files $1 = 404;

                include fastcgi_params;
                fastcgi_param SCRIPT_FILENAME $document_root$1;
                fastcgi_param PATH_INFO $2;
                fastcgi_param HTTPS on;
                fastcgi_pass 127.0.0.1:9000;
        }
}

Edit Kalkun’s file “application/config/config.php”:

$config['uri_protocol']	= "PATH_INFO";

Done!

This instructions will help you to create new self sign certificate and import it to your android device.

Due to a bug in android internal code you need some extra steps while generating your certificate. Otherwise your self-signed certificate will not show up under “trusted credentials” in android menu.

Create an auxiliary file “android_options.txt” with this line inside:

basicConstraints=CA:true

Create self-signed certificate using these commands:

• openssl genrsa -out priv_and_pub.key 2048
• openssl req -new -days 3650 -key priv_and_pub.key -out CA.pem
• openssl x509 -req -days 3650 -in CA.pem -signkey priv_and_pub.key -extfile ./android_options.txt -out CA.crt

Now our CA.crt certificate is almost ready.

Convert certificate to DER format:

• openssl x509 -inform PEM -outform DER -in CA.crt -out CA.der.crt

Import CA.der.crt:

• Put the CA.der.crt onto the sdcard of your Android device (usually to internal one). It should be in root directory.
• Go to Settings / Security / Credential storage and select “Install from device storage”.
• The .crt file will be detected and you will be prompted to enter a certificate name.
• After importing the certificate, you will find it in Settings / Security / Credential storage / Trusted credentials / User.

Just testing my new shining blogging software!

It was fun installing WordPress on Nginx with PHP-FPM