On Mar 2, 5:52 pm, Patrick Connolly
wrote:
> Any thoughts? I like the Git idea, and might pursue that, but wondering if
> anyone has input :)
If you're on EL you may want to look at cft[1]. I thought I saw
mention of work to bring ti to Deb based distros as well. I haven't
actually used it, but l
On Wednesday, March 2, 2011 at 5:52 PM, Patrick Connolly wrote:
Still trying to sort out whether this use-case even makes sense, but what if I
were to use Puppet to standardize development environments?
>
> It may be the case that someone makes a change or sets themselves up with a
> tool/config
Still trying to sort out whether this use-case even makes sense, but what if
I were to use Puppet to standardize development environments?
It may be the case that someone makes a change or sets themselves up with a
tool/configuration that allows them to work more efficiently. I can imagine
a sc
Thanks all for the responses. Sounds like basically the answer is
"you don't actually want the thing you are asking for", which after
hearing the reasoning I'm convinced is correct. I'm basically just
building out my puppet infrastructure now, which is why I was
interested in a feature like this,
On Nov 30, 6:58 am, gdb wrote:
> That is, does puppet have any
> support for propagating config changes from a client node back to the
> puppetmaster?
You mean so that the updated files will subsequently be served out to
clients? No, Puppet does not support that, and personally, I don't
find t
