Hi,
Is there a way to have the Chef server detect changes to the backing Git
repository and cause itself to up updated (whether cookbook, role, node,
etc. changes)?
Thanks,
Mark
Hi,
Is there a way to have the Chef server detect changes to the backing Git
repository and cause itself to up updated (whether cookbook, role, node,
etc. changes)?
Thanks,
Mark
On Wed, Feb 8, 2012 at 10:34 AM, mark bradley gopearls42@gmail.com wrote:
Is there a way to have the Chef server detect changes to the backing Git
repository and cause itself to up updated (whether cookbook, role, node,
etc. changes)?
I'm not clear on what you're asking.
If you have all your cookbooks and roles and whatnot stores on disk in
a traditional 'chef-repo' you are wondering if Chef could track that
git repo and import objects automatically?
If that's what you're asking, sometimes people have wanted something
where when they push their chef-repo to a central team repository,
they use git hooks there to run the proper knife commands to upload to
the server.
Otherwise, could you provide a fuller example please?
Bryan
Yes, that's exactly what I was asking about -- thanks for the pointer, I'll
look at git hooks now
Thanks,
Mark
On Wed, Feb 8, 2012 at 11:00 AM, Bryan McLellan btm@loftninjas.org wrote:
On Wed, Feb 8, 2012 at 10:34 AM, mark bradley gopearls42@gmail.com
wrote:Is there a way to have the Chef server detect changes to the backing Git
repository and cause itself to up updated (whether cookbook, role, node,
etc. changes)?I'm not clear on what you're asking.
If you have all your cookbooks and roles and whatnot stores on disk in
a traditional 'chef-repo' you are wondering if Chef could track that
git repo and import objects automatically?If that's what you're asking, sometimes people have wanted something
where when they push their chef-repo to a central team repository,
they use git hooks there to run the proper knife commands to upload to
the server.Otherwise, could you provide a fuller example please?
Bryan
Another way is to use a CI like Jenkins, and have a job that monitor
repository for changes and publish them automatically.
This way you will have history of what and when was published.
On 2/8/12 6:12 PM, mark bradley wrote:
Yes, that's exactly what I was asking about -- thanks for the pointer,
I'll look at git hooks nowThanks,
MarkOn Wed, Feb 8, 2012 at 11:00 AM, Bryan McLellan <btm@loftninjas.org
mailto:btm@loftninjas.org> wrote:On Wed, Feb 8, 2012 at 10:34 AM, mark bradley <gopearls42@gmail.com <mailto:gopearls42@gmail.com>> wrote: > Is there a way to have the Chef server detect changes to the backing Git > repository and cause itself to up updated (whether cookbook, role, node, > etc. changes)? I'm not clear on what you're asking. If you have all your cookbooks and roles and whatnot stores on disk in a traditional 'chef-repo' you are wondering if Chef could track that git repo and import objects automatically? If that's what you're asking, sometimes people have wanted something where when they push their chef-repo to a central team repository, they use git hooks there to run the proper knife commands to upload to the server. Otherwise, could you provide a fuller example please? Bryan
--
Vladimir Girnet
Infrastructure Engineer
Tacit Knowledge
I am trying to figure out a good way to deal with a dynamic pool of
web sites. Using the EC2 cloudfront I want to set up a dynamic pool of
web servers which would scale up and down as needed. At any time I
won't know how many machines there are.
I saw some documentation on using cloudfront and chef but it's quite
old so I am not sure if it's valid anymore. Any documentation on how
to dynamically register hosts and how to deploy code to an unknown
number of hosts anywhere?
Cheers
On Thu, Feb 9, 2012 at 10:08 PM, Vladimir Girnet
vgirnet@tacitknowledge.com wrote:
Another way is to use a CI like Jenkins, and have a job that monitor
repository for changes and publish them automatically.
This way you will have history of what and when was published.On 2/8/12 6:12 PM, mark bradley wrote:
Yes, that's exactly what I was asking about -- thanks for the pointer, I'll
look at git hooks nowThanks,
MarkOn Wed, Feb 8, 2012 at 11:00 AM, Bryan McLellan btm@loftninjas.org wrote:
On Wed, Feb 8, 2012 at 10:34 AM, mark bradley gopearls42@gmail.com
wrote:Is there a way to have the Chef server detect changes to the backing Git
repository and cause itself to up updated (whether cookbook, role, node,
etc. changes)?I'm not clear on what you're asking.
If you have all your cookbooks and roles and whatnot stores on disk in
a traditional 'chef-repo' you are wondering if Chef could track that
git repo and import objects automatically?If that's what you're asking, sometimes people have wanted something
where when they push their chef-repo to a central team repository,
they use git hooks there to run the proper knife commands to upload to
the server.Otherwise, could you provide a fuller example please?
Bryan
--
Vladimir Girnet
Infrastructure Engineer
Tacit Knowledge
http://www.tacitknowledge.com