Amanda waite wrote: > Danek Duvall wrote: >> I'm curious about the versioning of the paths. Do people actually install >> more than one of these on a system at a given time? I'll note that none of >> Ubuntu, Fedora, and Gentoo version their installations. Does the HTML >> documentation root really need to be versioned? >> > > We felt that it's very likely that users will want to run more than one > version of Lighttpd on the same system and so provisioned for it. In > doing so we tried to stick with many of the conventions that had already > been established with Apache2. The layout of the Lighttpd integration is > very similar to that of Apache2 including the versioning of the document > root. Once you've decided on having multiple versions then you really > have to version everything on the assumption that both versions would be > run simultaneously. > >> Are the executables you're shipping commonly run from the commandline? It >> seems from the manpages you provide that lighttpd is something that would >> most likely only ever be run via SMF, and that spawn-fcgi would only ever >> be run from lighttpd. Could *all* of the executable code live, better >> integrated with Solaris, under /usr/lib/lighttpd? >> > > Actually, it's as likely that users would want to run the spawn-fcgi > command as they would be to run the lighttpd command. spawn-fcgi is used > to spawn the backend end processes that Lighttpd connects to and is run > independently of the lighttpd command. Our initial thought was that the > command line tools were used so much that they should go in /usr/sbin > and /usr/bin but we were asked to look into it and found that they were > most likely to be run only while debugging. We then decided to hide away > the executables in /usr/lighttpd/1.4 and as you suggest, make SMF the > public interface for Lighttpd. The exact location was again determined > by the convention set by the Apache2 integration.
You usually only run lighttpd on by hand if you want to verify the configuration is valid (lighttpd -t ...) or want to print the configuration in a clean way (lighttpd -p ...). >> Why are you providing support for mysql, but not postgres? Will you >> include support for sqlite once it integrates? >> > > Lighttpd supports MySQL for the vhost module (which is actually called > mod_mysql_vhost) which allows users to host a vhost's docroot in a MySQL > DB, there is no equivalent module that supports Postgres. SQLite is used > only with the WebDAV module and we will certainly look at adding support > for that module once the integration of SQLite3 is complete. In the next major release (1.5) we have split out the db-backend: * mod_sql_vhost_core.c * mod_mysql_vhost.c * mod_postgresql_vhost.c the two are only providing the access to the storage, the core-module does the caching and everything else. cheers, Jan (lighttpd dev) -- jan: "Gee, Brain^WEric, what'd you wanna do tonight?" eric: Same thing we do everynight: Take over the HelloWorld!
