Hi D, I'm trying to pitch in and help, but may be way off base.
Konstrukt is a straight forward PHP framework, but one that
uses some Apache rules to work. You can find those rules in
the www/.htaccess file.
I've used lighttpd before but don't remember what its equiv
rules setup would be. My sense is that if you rig the equiv
lighttpd ruleset and otherwise setup a valid konstrukt
web site tht works w/ apache you should be good to go.
Thinking as I'm writing ... good place to start debugging
would be to use apache2 on a dev system w/ your app
to insure first of all that your app is functional w/ apache.
Then, when you know you're using konstrukt correctly,
shift over to lighttpd and start playing with its rules to
match the .htaccess rules.
I'm including a (believe normal) konstrukt .htaccess file here:
# Apache configuration file for Konstrukt
application
# These lines enables logging of errors to /log/error.log
php_value error_log "../log/error.log"
php_value log_errors on
php_value html_errors off
# Enable display errors in browser
# For a production site, set the following two lines to off
php_value display_startup_errors on
php_value display_errors on
# These settings routes all traffic, except concrete
files, to the dispatcher
DirectorySlash Off
Options FollowSymLinks Indexes
DirectoryIndex index.php
RewriteEngine on
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule ^.*$ - [L]
RewriteCond %{REQUEST_FILENAME} -f
RewriteRule ^.*$ - [L]
RewriteRule ^.*$ index.php [L]
Heitzso