Bug 444953 - Add support for a conf.d directory
Summary: Add support for a conf.d directory
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: lighttpd
Version: rawhide
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Matthias Saou
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-05-02 10:11 UTC by David Dick
Modified: 2008-12-22 16:22 UTC (History)
0 users

Fixed In Version: 1.4.20-2
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-12-22 16:22:11 UTC


Attachments (Terms of Use)
Patch to include conf.d support for lighttpd (281 bytes, patch)
2008-05-02 10:11 UTC, David Dick
no flags Details | Diff

Description David Dick 2008-05-02 10:11:41 UTC
Description of problem:

/etc/lighttpd/lighttpd.conf provides no interface for packaging a web
application for lighttpd.  By convention this is done by providing a conf.d
directory.

Version-Release number of selected component (if applicable): 1.4.19-4.fc8


How reproducible:


Steps to Reproduce:
1. examine /etc/lighttpd/lighttpd.conf
2. search for conf.d directory
3.
  
Actual results:

no conf.d directory capability is observable

Expected results:

patch included. background discussion from lighttpd developers at
http://trac.lighttpd.net/trac/ticket/1221

Additional info:

Comment 1 David Dick 2008-05-02 10:11:41 UTC
Created attachment 304372 [details]
Patch to include conf.d support for lighttpd

Comment 2 Bug Zapper 2008-05-14 10:30:39 UTC
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 3 Matthias Saou 2008-12-22 16:22:11 UTC
Added in 1.4.20-2, only in devel for now. Note that from my testing, this makes it quite hard to find the errors in the conf.d/*.conf files since lighttpd reports the error as being on the include_shell line from the main configuration. But I understand how useful this can be, which is why I've included the change.


Note You need to log in before you can comment on or make changes to this bug.