Lighttpd

lighttpd is a very flexible and modular web server. There is no "one-size-fits-all" configuration, though there could be "one-size-fits-most" or even better, "a-few-options-fits-most". What do you think those would be? Some people have provided examples on github: https://github.com/search?q=lighttpd&type=registrypackages

This would allow lighttpd to be available on operative systems that do not provide official packages

Do you have some examples where lighttpd is not provided? (OTOH, I know of many examples of distros where the lighttpd package is outdated.)

without requiring users to compile from source.

I realize that is a barrier to entry, but have you tried? lighttpd source code and build instructions

My concerns are specifically to address the so called barrier of entry and to welcome more users to lighttpd.

But to answer your questions:

- lighttpd is not shipped by rhel, though it is available on the EPEL as a community package and depends on another EPEL package compat-lua. Packages that are not officially supported are not trusted by users as officially supported ones.

Regardless, the web servers that RHEL does support (apache httpd and nginx) also have officially supported docker images. Container images are used for more than just local installs, as you may be aware.

- I have tried, I don't have a problem with it, but the process can be much easier and serve more purposes.

Thanks for the feedback! I do agree with you, though please understand that my time is a finite resource.

Since Fedora lighttpd package for 1.4.63, lighttpd.spec uses lua instead of compat-lua.

Hopefully soon, lighttpd will be part of EPEL 9, though DBI support will have to wait for a future EPEL major release.