Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rethink the whole cron/update-everything malarky #19

Open
gravitystorm opened this issue Nov 18, 2014 · 0 comments
Open

Rethink the whole cron/update-everything malarky #19

gravitystorm opened this issue Nov 18, 2014 · 0 comments

Comments

@gravitystorm
Copy link
Contributor

Time have changed since 2011!

We should normalize the way these chef cookbooks work to match current best practices, so that anyone wanting to contribute has as few surprises as possible. The update-everything.sh bash file is the antithesis of expected behaviour.

We should distribute cookbooks to the machines running cyclescape using a chef server, and we should run the standard chef-client on each machine to handle the chef runs. This will also make it easier to integrate with chef testing tools without having to bodge them into our current peculiar setup, and allow people install cyclescape using a standard chef setup.

This was referenced Nov 18, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant