I’m going to redirect http://blog.rootninja.com to the main site. I don’t know why I didn’t just do this in the first place. I’ve always left it over here on its own. But it’s all on the same Virtual private server. Anyway, this is really easy to do in lighttpd. First, redirect all “www.rootninja.com” traffic to “rootninja.com”, because that other page is useless.

Automatic updates of plugins and wordpress itself does not work with lighttpd out of the box. No matter how much I searched for an answer to why this was happening, I couldn’t seem to find anyone that addressed the problem and came up with a solution. I wanted to fix …

‘ve seen many ways to solve wordpress url rewriting for lighttpd. Some people say all you need a server.error-handler-404 = “/index.php” and you’re done, but that didn’t work for me. If you’re trying to run several sites using multiple domain names with multiple installation directories, here’s how I got it to work. But take this with a grain of salt because your mileage may vary. /cliches
First make sure you include the broken-scriptfilename line in your fastcgi line. That was key to getting skins working for me.

There’s a few packages you might not have installed that you’ll need before php phpMyFAQ will install. On a basic, headless virtual machine, I don’t install a web server, php or databases by default. So I’ll start from there.

I moved a database over to another server and setup php and lighttpd, but authentication for my app wasn’t working.

Enabling aliases in Lighttpd is even easier than in Apache. If you want to browse your app without having to include the trailing slash, then make sure you didn’t include trailing slashes in your alias definitions (my alias.url’s above don’t have the trailing slash). Many examples show something like /doc/ => “/usr/share/doc/” but then it won’t find the index.php or index.html on its own.

I read in a bunch of places that you can’t use HTTP["scheme"] to redirect http:80 traffic to https:443 without using 2-3 levels of nesting with socket and host. But that’s just not true. The only reason it doesn’t work at first is because http is a subset of https, so be more specific with http$ and it works with just one line in lighttpd.conf.

Now edit the lighttpd.conf configuration file to enable ssl. Use the public facing interface’s IP address instead of mine, unless yours happens to be 192.168.1.2 too! And nmap or netstat will let you know it’s listening on port 443

Enabling LDAP authentication should take you about 2 minutes, unless you type with just 2 fingers. Then maybe 3 or 4. …If you don’t allow anonymous connections to your ldap, give it a user/password combination that has enough privs to do the lookups, or just use your master account if you’re just testing or don’t really care. … Now tell it what parts of your webserver you want to protect and how. You can specify any string you’d like for the realm. Here I require an LDAP user account name and password just to get to the wiki main page, and only admin can see the server-config page… Restart lighttpd and you’re done.

blah blah, mediawiki http://blog.rootninja.com, And finally, “To complete the installation, move config/LocalSettings.php to the parent directory.” just like it says…