Hey
I went with my option #2 for this exercise. I will definitely be looking into
the package management as it'll come up. In fact, it may have already come up
in a different request. For this one, though, I have something like 5 scripts
in the 'all-hosts' list and 3 in the subset so
On Mon, 15 Aug 2016, dkoleary wrote:
Hey;
Thanks for the responses. I hadn't thought of packages. I will start
exploring that option
What would work, as a short term option:
* A class that just owns /root/bin
* Separate classes that create things in directories under /root/bin (say
Hey;
Thanks for the responses. I hadn't thought of packages. I will start
exploring that option
Thanks again.
Doug O'Leary
On Monday, August 15, 2016 at 3:42:20 PM UTC-5, Rob Nelson wrote:
>
> Doubt,
>
> I agree with Dan, packaging is the answer. And before you say it - yes,
> packaging
Doubt,
I agree with Dan, packaging is the answer. And before you say it - yes,
packaging sounds scary at first, but it doesn't have to be. Check out FPM -
https://github.com/jordansissel/fpm/wiki - to generate a package in the
correct format. You can very easily package static files that way, and
On Mon, 15 Aug 2016, dkoleary wrote:
Hey;
I suspected this was going to be a problem and, sure enough, it is.
Here's the scenario: puppet server 4.5: I have ~ 1200 hosts on which I
want specific files in /root/bin on all hosts. A reasonably large subset of
those should have additional
Hey;
I suspected this was going to be a problem and, sure enough, it is.
Here's the scenario: puppet server 4.5: I have ~ 1200 hosts on which I
want specific files in /root/bin on all hosts. A reasonably large subset
of those should have additional files in /root/bin as part of an
