[Pkg-puppet-devel] should config.ru be a conffile?

[Nigel Kersten]

On Tue, Sep 14, 2010 at 10:15 AM, Mathias Gug <mathiaz at ubuntu.com> wrote:
> Hi Nigel,
>
> Excerpts from Nigel Kersten's message of Tue Sep 14 12:13:49 -0400 2010:
>> On Thu, Sep 9, 2010 at 11:09 AM, Mathias Gug <mathiaz at ubuntu.com> wrote:
>>
>> >> It looks like code, but it isn't really much of that. You generally
>> >> just set config options there and then start the relevant application.
>> >>  It used to be a lot of code with 0.24.x, but not really in 0.25
>> >>
>> >> I think your suggestion is feasible, but I personally think it
>> >> diverges us too much from upstream for too little gain, and the
>> >> interaction between options in the config file, config.ru and command
>> >> line have had too many edge cases upstream for me to feel really
>> >> confident.
>> >
>> > Fair enough. It seems that moving config.ru to
>> > /etc/puppet/rack/config.ru is a wise choice then.
>>
>>
>> Do we want to try and fix this situation for 2.6.1 now that it's been
>> released? Or should we not do that during a point release?
>>
>> If we're ok with doing it, I'll get the work done today.
>
> How about targeting experimental (and put the work in the master branch)
> for now?
>
> If it turns out to be simple it could be backported to the squeeze
> branch.

So I'd like some Debian-Best-Practices advice here now that I've done
some symlink tests, which all work.

the rack directory for puppetmasterd/passenger is analogous to an
Apache virtualhost DocumentRoot as I see it, thus it really doesn't
belong in /etc.

However we want the config.ru file to be a conffile, and thus it needs
to belong in /etc.

Where is the appropriate place for the rest of the rack directory contents?

something like:

($vardir is the puppet vardir, not /var)

$vardir/rack/puppetmasterd
$vardir/rack/puppetmasterd/config.ru -> /etc/puppet/config.ru
$vardir/rack/puppetmasterd/public
$vardir/rack/puppetmasterd/tmp

?