Re: [Puppet Users] Re: Module structure for case-specific configuration

2013-04-17 Thread Boyan Tabakov
On 16.4.2013 16:30, jcbollinger wrote: > [... which carries maintenance costs typical of such boilerplate > repetition.] > > It sounds to me like requiring an explicit declaration for each project > class is the way to go. As I said already, however, that's entirely > unrelated to the question of

Re: [Puppet Users] Re: Module structure for case-specific configuration

2013-04-16 Thread jcbollinger
On Tuesday, April 16, 2013 3:52:40 AM UTC-5, Boyan Tabakov wrote: > > > It is not website related components, but indeed web-server - vhost > definitions, special apache configuration files (e.g. module > configuration overrides, etc). Besides, the apache was just an example, > I have other ca

Re: [Puppet Users] Re: Module structure for case-specific configuration

2013-04-16 Thread Boyan Tabakov
Hi John, Thanks for your reply! On 15.4.2013 18:02, jcbollinger wrote: > Single point of entry does not serve well and is not a particularly > useful goal when the desired results are very divergent. The single > declaration then becomes magical, and therefore difficult to understand > and maint

[Puppet Users] Re: Module structure for case-specific configuration

2013-04-15 Thread jcbollinger
On Monday, April 15, 2013 5:02:06 AM UTC-5, Boyan Tabakov wrote: > > Hi all, > > Let's consider the following situation: > > I use the module structure, proposed by R.I.Pienaar: > > http://www.devco.net/archives/2012/12/13/simple-puppet-module-structure-redux.php > > > I have a module, let's