Consider using Lua as the configuration file language.

[wjl@…]

Consider using Lua as the configuration file language.

Lighttpd already uses and supports Lua for some things (e.g. mod_magent). However, there are a lot of other things that are really ad-hoc, like the lighttpd configuration file which has a number of quirks and limitations.

It would be possible to support this while still keeping backwards compatibility, by simply having a Lua configuration function that can include legacy configuration files, so people only need to upgrade if they want to (e.g. they could keep their old setup and just have their master Lua configuration file just including their old config file).

Doing this also has the advantage that it would simultaneously solve almost every open bug against configuration file quirks, since everything would just be driven by Lua.

Anyway, please consider this, even if it's for 1.5.x or 1.6.x =)

[MikhailMiguel]

Please, staff: don't forget it! Is a really great idea!

[stbuehler]

The 1.x config system is the limitation, not the config file itself. so lua wouldn't help there.

in 2.0 there will be a new config system with a lua frontend. but for 1.x this is a wontfix.