+1 I tea what you did there.
On Tue, Sep 15, 2015 at 11:12 AM, Corey Osman wrote:
> +1 Sounds tearrific.
>
> On Monday, September 14, 2015 at 10:36:56 AM UTC-7, Felix Frank wrote:
>>
>> On 09/13/2015 10:17 AM, Erik Dalén wrote:
>> > Want to join? Throw a +1 in the list so I get a rough idea of
Neat idea. I would consider using this for automatic git-checkout of
project branches, rather than preemptively checking out all branches by
cron or git-hook.
On Thu, Mar 12, 2015 at 3:33 PM, Bostjan Skufca <
bostjan.skufca.w...@gmail.com> wrote:
>
>
> On Thursday, 12 March 2015 20:30:23 UTC+1, J
On Wed, Apr 16, 2014 at 11:53 AM, Andy Parker wrote:
> On Tue, Apr 15, 2014 at 1:20 PM, Erik Dalén
> wrote:
>
>> Another way to improve it would be if the % and-or <> flags were passed
>> to the ERB builder. % enables Ruby code processing for lines beginning with
>> %. <> omit newline for lines
This looks awesome, great work!
On Tue, Jul 23, 2013 at 3:28 PM, Pawel Tomulik wrote:
> W dniu wtorek, 23 lipca 2013 16:29:34 UTC+2 użytkownik Pawel Tomulik
> napisał:
>
>> Hi,
>>
>> I'm trying to adapt puppetlabs/apache module to work with apache 2.4 on
>> FreeBSD. I've already created a branch
What doesn't work as the code currently stands and needs to be changed?
Just to understand the scope of work that you might need to do to port the
module.
On Tue, Jul 23, 2013 at 7:29 AM, Pawel Tomulik wrote:
> Hi,
>
> I'm trying to adapt puppetlabs/apache module to work with apache 2.4 on
> Fre
You can use an external node classifier to determine configuration of a
machine by its hostname. Puppet Dashboard and similar tools can help to
manage the ENC process.
http://docs.puppetlabs.com/guides/external_nodes.html
https://puppetlabs.com/puppet/related-projects/dashboard/
Cheers,
Aaron
Are you referring to Puppet dashboard here, or Puppet server itself? It
looks like you've listed a bit of both.
On Fri, Apr 5, 2013 at 2:40 AM, Venky Acharya wrote:
> Where can i find a list of REST API's for puppet opensource?
>
> I am looking for following set of operations to be performed th
Here are the bugs queued for the Dashboard 1.2.23 release, closed bugs that
were resolved in recent releases, and rejected bugs that aren't likely to
happen.
There were a spate of security releases between 1.2.18 and the upcoming
1.2.23. The security releases did not pick up code merged to master
I just read through lib/puppet/provider per your footnote 3. It looks a
little over-engineered. I'm not sure how to approach threading an argument
hash through that many layers. I'm not even sure why there are so many
layers of wrappers there.
Awesome that you're digging into the git vcsrepo modul
And we're enabled for Dashboard, too! Thanks for setting this up!
Cheers,
Aaron
On Sun, Jan 6, 2013 at 11:08 AM, Jeff McCune wrote:
> Hi everyone,
>
> I've configured Github and Travis CI to automatically run the behavior
> examples against pull request branches for Puppet, Facter, Hiera, and
I read through the open Dashboard bugs this week, and made an effort to
close out resolved, out of date, or not-going-to-happen bugs. In a few
cases, I erred on the side of closing an issue rather than leaving it open
for years without action. Apologies in advance if I close your favorite bug
in my
I just merged a great feature contributed by Glenn Poston: On the Reports
page, tabs to show reports of only a particular type, all, changed,
unchanged, failed, pending.
For screenshots, see
https://github.com/puppetlabs/puppet-dashboard/pull/112#issuecomment-11506921
More features and bug report
Hi all,
I've received official commit bits as a community contributor to Puppet
Dashboard. My major work so far has been porting Puppet Dashboard to Rails
3 and Ruby 1.8.7/1.9.3, with complete clean-running specs. I'm really
excited about bringing some new energy to the Dashboard! My rails3 bra
13 matches
Mail list logo
