Hi Jon,
On 02/26/2012 10:17 AM, Jonathan Proulx wrote:
> Hi All,
>
> I'm building out my first puppet install and obviously want to
> leverage modules from the forge. Since I'm using git as the VCS for
> my puppet configs and most community modules are hosted on github it
> seems the obvious thin
On Sun, Feb 26, 2012 at 2:18 PM, Jonathan Proulx wrote:
> On Sun, Feb 26, 2012 at 1:54 PM, Brian Troutwine wrote:
>> I'm a big fan of using read-only submodules, usually to the upstream
>> project but sometimes to my own fork. The use of submodules makes
>> getting changes in from upstream trivia
On Sun, Feb 26, 2012 at 1:54 PM, Brian Troutwine wrote:
> I'm a big fan of using read-only submodules, usually to the upstream
> project but sometimes to my own fork. The use of submodules makes
> getting changes in from upstream trivial
I agree that github is where it's at. On of the things I l
I'm a big fan of using read-only submodules, usually to the upstream
project but sometimes to my own fork. The use of submodules makes
getting changes in from upstream trivial. The commands you need to
know are:
git submodule add
git submodule sync
git submodule update --init --recursi
Hi All,
I'm building out my first puppet install and obviously want to
leverage modules from the forge. Since I'm using git as the VCS for
my puppet configs and most community modules are hosted on github it
seems the obvious thing to do is to use either git submodules or
subtree merging, but I h
