[chef] Best practice to maintain chef-repo for a single node that hosts multiple rails app.


Chronological Thread 
  • From: millisami r < >
  • To: chef < >
  • Subject: [chef] Best practice to maintain chef-repo for a single node that hosts multiple rails app.
  • Date: Fri, 13 Jan 2012 18:46:31 +0545

Hi, I went through the Quick Start guide for radiant rails app deployment at and I did installed it correctly.

The files at data_bags/apps/radiant.jsonroles/radiant.rb and cookbooks/radiantall uses radiant as a base app name.

Now I am trying to create another radiant app (say: another_radiant). Here I am confused how to go ahead if I have to host another 3rd radiant app. This seems perfectly to go the Data Driven App Deploys way.

Looking inside the above rails stack, its name is radiant as cookbook, databags and roles as well.

So, for the new radiant stack app named another_radiant, do I have to copy those allradiant components into another_radiant for all cookbook, databag and roles too?

Or is there any better way so that it will be flexible to maintain across many servers?


@millisami
~Sachin Sagar Rai
Ruby on Rails Developer
http://tfm.com.np
http://nepalonrails.tumblr.com




Archive powered by MHonArc 2.6.16.

§