Lighttpd

What is intention of "var.server_root"

Configuration: Using variables

Yes I'm trying to get lighttpd up to serve a Dokuwiki service.

Please recognize that this is not a support site for Dokuwiki (or fill-in-the-blank any other random application)

Yes thank you, thusly I was asking about the intent of "var.server_root" as opposed to "server.document-root"

But I'm also being up front about why I've changed "server.document-root" just in case any experienced users might wish to tell the novice (me) of some common errors or gotcha other people have fallen for while trying to get lighttpd serve dokuwiki content.
My guess is that some experienced users might be able to predict that many new users are trying to get lighttpd to successfully serve html & php documents from a "A" (server.document-root) directory and also have php-fpm read/write data from a "B" directory to produce the html output for the "A" directory php pages.

gstrauss wrote in RE: What is intention of "var.server_root":

What is intention of "var.server_root"

Configuration: Using variables

Yes I'm trying to get lighttpd up to serve a Dokuwiki service.

Please recognize that this is not a support site for Dokuwiki (or fill-in-the-blank any other random application)

just in case any experienced users might wish to tell the novice (me) of some common errors or gotcha other people have fallen for

The most common mistake is a failure to use a search engine to search for simple terms like "dokuwiki" and "lighttpd"

https://www.dokuwiki.org/install:lighttpd
https://www.dokuwiki.org/install:lighttpd_config_example

lighttpd mod_fastcgi

Below is response I was writing ; my delay was because I'm still double checking what the flick is happening and whether there's documentation for it.
Right thank you. My apology I responded to the email and the html formatting tended to make only your last line stand out.

I suspect I had a false impression lighttpd ignored a conf setting to serve on port 90, suspect it wasn't running because it didn't see the lighttpd.conf file which is unusual behaviour - I had expected it to just go to default settings if it didn't see the configuration directory.

Currently I'm having to force it with "lighttpd -f /usr/local/etc/lighttpd/lighttpd.conf"