Structure the README with project status

[LeoColomb]

Shall we archive GAE and lighttpd?

[LeoColomb]

@roblarsen 😊

[gstrauss]

Shall we archive GAE and lighttpd?

Why archive lighttpd? lighttpd is actively maintained (hi! I am a lighttpd developer) and is the default webserver on many small systems, e.g. RaspberryPi, and embedded systems.

That said, https://github.com/h5bp/server-configs-lighttpd/blob/master/lighttpd.conf could use some minor updating.

[roblarsen]

@LeoColomb to me, if the configs aren't useful, then we should archive them. If they're still useful and just stale, that's okay. I don't know enough about either tech to make that call.

[LeoColomb]

Why archive lighttpd?

@gstrauss I'm talking about H5BP config for lighttpd of course, not lighttpd by itself on which we have literally zero right to archive anything. 🤔
But glad to hear you are the maintainer! 👋 Are you interested into maintaining that H5BP config boilerplate as well?
Or even better, is it possible to make lighttpd default values as close as possible from current web standard recommendations? I have no idea how much (or how little) it deviates from these recommendations today, but another (and better) way to maintain H5BP configs is to make them widely irrelevant with solid default config. 💪

@roblarsen That's fine for me, then the PR is ready 😊

[gstrauss]

I submitted PR yesterday: h5bp/server-configs-lighttpd#4

There is no one-size-fits-all web configuration, though there are conventions and a generic recommended starting config.

The PR I submitted generally kept the same caching settings as the prior config, even though caching settings can be very site-specific.

[gstrauss]

Or even better, is it possible to make lighttpd default values as close as possible from current web standard recommendations?

There are literally thousands of pages of HTTP-related RFCs.
Depending on the site frameworks, there are thousands of more pages discussing best practices. Best practices for security. Best practices for mobile. Best practices for widest browser compatibility. ... some of these best practices make tradeoffs, and some conflict with other recommendations, depending on what you prioritize for your site.

I have no idea how much (or how little) it deviates from these recommendations today, but another (and better) way to maintain H5BP configs is to make them widely irrelevant with solid default config.

lighttpd aims to be RFC-compliant by default and the lighttpd default config template shipped with lighttpd source code does so. However, there are many, many, many optional features to HTTP RFCs and lighttpd configuation. There is no one-size-fits-all.

FYI: the most basic lighttpd config is a single line which specifies from where to serve files: server.document-root = "..."

[LeoColomb]

@gstrauss Let's continue the discussion on h5bp/server-configs-lighttpd#5 😊
@roblarsen Let me know about the pull request 😊

[roblarsen]

👍

[LeoColomb]

(@roblarsen I can't merge on this repo, or do anything else actually 😅)

[roblarsen]

@LeoColomb I just added you to the correct team to manage this repo. You should also... manage that team! I don't know half the people myself, so you might know better than I do if those people should still have access.