search

mm53bar / plow

Deploy your app with bash
5 stars 2 forks source link

Keeping a history of what's been ran on the server #27

Open ryanjones opened 11 years ago

ryanjones commented 11 years ago

We recently had a problem where a staging box was out of sync with prod (the recipe had been forgotten to run on the prod box).

I wonder if there's a way we could keep track (on the server) what recipes have been ran. And a way where we could give and array of servers and check to see if they're running the same thing.

Thoughts?

/cc @jbabe @mm53bar @MarkBennett

MarkBennett commented 11 years ago

@cbrualk CC

MarkBennett commented 11 years ago

Perhaps we could have a log on boxes provisioned with plow that recorded when plow is run? A more correct solution would probably be to record a version for each plow recipe and then track the latest version of each recipe run on each box so we could interrogate them in the future, but there would be a lot of leg work to set that up.

I think this is why both Chef and Puppet focus on resource descriptions rather than using script the way plow does. It's harder to setup but it makes this kind of auditing possible.

Mark Bennett Burmis Studio Inc. BUSINESS SOFTWARE DEVELOPMENT

(Phone) 780.862.6275 (Twitter) http://twitter.com/markbennett (Email) mark@burmis.ca (Website) http://burmis.ca (Gtalk) mark@burmis.ca

On Tue, Aug 13, 2013 at 1:00 PM, Ryan Jones notifications@github.comwrote:

We recently had a problem where a staging box was out of sync with prod (the recipe had been forgotten to run on the prod box).

I wonder if there's a way we could keep track (on the server) what recipes have been ran. And a way where we could give and array of servers and check to see if they're running the same thing.

Thoughts?

/cc @jbabe https://github.com/jbabe @mm53barhttps://github.com/mm53bar @MarkBennett https://github.com/MarkBennett

— Reply to this email directly or view it on GitHubhttps://github.com/mm53bar/plow/issues/27 .