On 11/25/2012 8:50 AM, Mark wrote:
So you would recommend, when possible, to shove everything into one file? Say there is a lengthy and/or complex implementation… are there any general best practices to adhere to?Also as a general guideline should one try and include all dependencies at the module level or at the node level? For example, I have a rails application that depends on nginx. Should I model that dependency in the node like: node web { include nginx include rails } Or should it be modeled like: node web{ include rails } class rails { include nginx } Once again, thanks for your input.
Depends on your infrastructure. If you always use nginx with rails, then include ngnix within the Rails class makes sense. Of course you may create a new hostgroup sometime in the future that needs Rails and does not need nginix that will require you to make some changes. However I think you'll get far more work done if you just plow ahead and don't worry too much about having to refactor later. You'll have to do it regardless because no system you create is going to be (or needs to be) that flexible.
Also it's poor etiquette to ask your questions repeatedly on other people's threads. Create a new thread for your question.
Ramin -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
