Matt Ingenthron wrote: > Hi Amanda, > > Amanda Waite wrote: >> Hi Matt, >> >> See: http://redmine.lighttpd.net/issues/1221 > > Thanks for the pointer. The idea of using cat had come up, but > obviously the lighttpd.conf shipped with Web Stack would have to do that. > > It feels wrong for me to squash the built in lighttpd.conf with the > one in my package, but I guess that's the right thing to do?
Well you could ship another SMF manifest/method that start lighttpd with a config file from a different location. That way you could create a service with a name meaningful for your package and use your custom config file without touching the default lighttpd config file. Clobbering the default config file might not be popular with those that have already customised it, but then if they have they are probably running lighttpd in such a way that the SMF idea won't work either (maybe using port 80 already). Amanda > In my case, the intended configuration would only run lighttpd, so I > guess it's not that bad. Without postinstall scripts, this seems to > be my only choice. I can at least just replace it with a 'stock' one > which includes my configuration from conf.d. > > Good to know I wasn't missing anything. Thanks for the help! > > - Matt >
