#2011 reconfigure lighttpd
Closed: MIGRATED a year ago by nikromen. Opened 2 years ago by praiskup.

There are several cool things proposed in:
https://pagure.io/fedora-infra/ansible/pull-request/903

We should long term take a look at them, use them, and test properly:

  • consider using max-workers = 0
    • stop using piped logger
  • lua handler for the log files
  • stop using our own cipher-list, we should check that lighttpd really uses the
    PROFILE=SYSTEM by default
  • use the standard ssl files (not the combined *pem, it complicates
    our roles/copr/certbot role)
  • try to use up2date config file (perhaps we shouldn't maintain the
    lighttpd.conf in our code, and modify what is shipped by lighttpd
    package)
  • we can consider switching to JavaScript footer, from serverside PHP

Thanks to @gstrauss for all the feedback!


Metadata Update from @praiskup:
- Issue priority set to: None (was: Low)

2 years ago

lighttpd-1.4.63-1 is available in Fedora 34, Fedora 35, and Rawhide
https://packages.fedoraproject.org/pkgs/lighttpd/lighttpd/

Please consider testing and scheduling upgrade, then incrementally implementing some of the enhancements in this pull request, starting with server.max-worker = 0 (or delete server.max-worker)

lighttpd-1.4.64-1 is available in Fedora 34, Fedora 35, and Rawhide
https://packages.fedoraproject.org/pkgs/lighttpd/lighttpd/

Please consider testing and scheduling upgrade, then incrementally implementing some of the enhancements in this pull request, starting with server.max-worker = 0 (or delete server.max-worker)

@praiskup @frostyx

Fedora 36 ships with lighttpd 1.4.64 and Rawhide has lighttpd 1.4.65.

Please consider testing and scheduling upgrade, then incrementally implementing some of the enhancements in this pull request, starting with server.max-worker = 0 (or delete server.max-worker)

Metadata Update from @nikromen:
- Issue close_status updated to: MIGRATED
- Issue status updated to: Closed (was: Open)

a year ago

Login to comment on this ticket.

Metadata