- From: Jacobo García <
- Subject: [chef] Mantaining several chef repositories.
- Date: Mon, 28 Dec 2009 01:20:05 +0100
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:from:date:message-id:subject:to:content-type; b=Lanqhl21AR6/f+VHCnsS+lipxCno6D+3L0yPlQGo+z5LxOOQytSvF0di5LXxT6skun Ur480aW42ZEQdXTP9YoYcxKeIYVWv9yQXU9NRM7WZ9/wcXROIytg3HnLwhmZ+KUW//vn nkNTy8UoYooOlUI8mrHPePFNaL5kAw6Dv3uN0=
I have a problem partially related to chef (it's also a git problem) but I think i'll get better answers in the chef list than in git's one.
The problem is that I have to mantain different chef repositories since I'm doing chef work for a couple of companys and also I want to publish recipes code to github. I am looking for strategies to do this.
All repositories share the same code except what I call 'sensible data', (passwords, certs, etc...) So 95% of the files in the repository are exactly the same except those ones. What's the best way to keep this sensible files private to my clients and also be able to spread changes between repositories?
Thank you very much.
- [chef] Mantaining several chef repositories., Jacobo García, 12/27/2009
Archive powered by MHonArc 2.6.16.