Why can't it show the diff / update like dpkg does?
nobody has done it yet.
So how does it handle updated conf files?
I'm not entirely sure. It runs dpkg in non-interactive mode, which means it
would either overwrite configs without asking (and then overwrite them again
with what's in the Puppet repo) or flag it as an upgrade failure and require
manual intervention.
Personally I have configured Puppet not to upgrade anything automatically so I
can do distro upgrades by hand, as I only have a small number of servers to
maintain. People with large numbers of servers may automatically upgrade one
or two, test them, fix any problems by updating the config repo, then upgrade
the rest with the fixed config.
The code is Debian specific but the resulting lighttpd options aren't. If
you're using Puppet to configure lighttpd you are unlikely to want to
autoconfigure IPv6,
Why? Are IPv6 and Puppets no friends?
Sorry, let me rephrase - if you are using Puppet to configure lighttpd, you
almost certainly don't want IPv6 support left as 'autodetect'. You will
either enable it or disable it. The Debian script only enables IPv6 if it is
available, which is great for having it 'just work' on a newly installed
machine which may or may not have IPv6 available. However people going to the
effort of using Puppet to manage their configuration generally want to know
exactly how each machine is configured, and setting things to autodetect
introduces some unpredictability into the mix.
For example if you want to deploy an IPv6 capable web server and for some
reason the machine doesn't have IPv6 support, the Debian script would happily
start lighttpd in IPv4-only mode, and you would not realise the mistake until
someone reported that they could not connect to the server over IPv6. But if
you forced IPv6 on in the lighttpd config, it should fail to start without
IPv6. Your other monitoring tools would then pick up that lighttpd wasn't
running and alert an admin for an immediate fix.
Cheers,
Adam.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
