Net :: lighttpd



I'm working on a lighttpd.uci extension, which currently works fine in DSL as far as I can tell.  For my own limited needs it has everything I'd use in a default build, but wondering if other DSL users might prefer it to be more full-bodied.

The default build has the following:

       + IPv6 support
       + zlib support
       + bzip2 support
       + crypt support
       - SSL Support
       + PCRE support
       - mySQL support
       - LDAP support
       - memcached support
       - FAM support
       - LUA support
       - xml support
       - SQLite support
       - GDBM support

pcre support is supplied by including an additional library that isn't available in DSL (pcreposix apparently doesn't work with lighty), but I'm not sure how vital it is. According to the docs, it's used for =~ and !~ in conditionals and for regex matches in url.rewrite and url.redirect.  Sounds like something that will not cause problems if disabled, but could make configuration less flexible.

openssl support is disabled by default, and it seems that some features don't work well with it.  Is SSL important for a light httpd?  I can't think of any reason i'd need it myself, but what about other users?

xml and sqlite are used for property storage for mod_webdav...no idea what that means.

I have no idea what any of the other stuff is for either.  I made a build with lua, xml, and sqlite enabled just because DSL has them, but I'm starting to think they are fairly useless in a typical small webserver.

Regardless of what feedback I get, this package won't be built with mysql support.  It's a fat package and I'm not going to install it just so i can include support for it in a web server =o)
Well...with no responses, I'm going to assume that either there is little interest, or most people don't know or care any more than I do.

So I'm leaving it with the default features, at least for now.  I've been messing around with it for the last few days, and so far it seems like a very good server.  There are at least a few things I need to learn more about before I'm comfortable with releasing a mydsl, so it'll probably be a week or so before it's submitted.
http://en.wikipedia.org/wiki/WebDAV sounds nice, but I wonder how practical it is.

I'd say ssl support _should_ be incorporated (for passwords and such? You can never be too secure :p ), but seeing how DSL doesn't use the newer libraries, it may be better not to incorporate them (for a better bug-free experience).

So I'll say the defaults should be fine.  Haven't tried this httpd yet (Apache user), but I did hear some good things about it.  How large are your preliminary packages?
I had already compiled a binary with webdav-props in order to enable Lua and SQLite.  It seems that this is all Lua and SQLite are used for, and i had no idea what webdav is, so i went back to the defaults.

I don't recall exactly what it was, but there was at least one lighttpd feature that was said to be troublesome with ssl.  I may still compile with ssl support anyway. Since I have to use LD_LIBRARY_PATH to include libpcre, another lib or two shouldn't be a big deal...as long as it doesn't add too much to the package.

So far I'm testing with uncompressed files, and gradually adding files for testing/demonstration, so I don't have any idea how big the package will be.  At this time the essential files are a little under 600k and there are an additional 350k in docs and tests
Wow.. that size is pretty light indeed.

Just a thought: if you want something, or not sure about something you want to be enabled, but the module is too large, you could always compile with that being supported, then create an "add-on" package.  Maybe?  Or it might get too complicated then, heh.
Next Page...
original here.