Re: [Puppet-dev] Re: Puppet 5 changes

2015-03-06 Thread Trevor Vaughan
John, Felix, and I agreemarking on calendar On Fri, Mar 6, 2015 at 12:12 PM, Felix Frank < felix.fr...@alumni.tu-berlin.de> wrote: > Seconded. For debugging purposes, the webrick master is still useful as > well. > > On 03/06/2015 06:04 PM, Trevor Vaughan wrote: > > I was going back and f

Re: [Puppet-dev] Re: Puppet 5 changes

2015-03-06 Thread Felix Frank
Seconded. For debugging purposes, the webrick master is still useful as well. On 03/06/2015 06:04 PM, Trevor Vaughan wrote: > I was going back and forth on this and I have to agree with John. > > There have been several times where I pushed out a lightweight Puppet > server on a VM running 512M R

Re: [Puppet-dev] Re: Puppet 5 changes

2015-03-06 Thread Trevor Vaughan
I was going back and forth on this and I have to agree with John. There have been several times where I pushed out a lightweight Puppet server on a VM running 512M RAM, 1 CPU, just to try something in a 'production-like' scenario. I'm OK with losing Rack support, but a lightweight server instance

[Puppet-dev] Re: Puppet 5 changes

2015-03-06 Thread John Bollinger
On Thursday, March 5, 2015 at 10:30:47 PM UTC-6, Eric Sorenson wrote: My hypothesis is if you're just dipping a toe in the water to try out > Puppet, running standalone with `puppet apply` is probably going to work > better than a webrick agent/server setup. > > I'm doubtful of the validity