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

How to manage production configuration? #1

Open
wbingli opened this issue Sep 12, 2013 · 3 comments
Open

How to manage production configuration? #1

wbingli opened this issue Sep 12, 2013 · 3 comments

Comments

@wbingli
Copy link

wbingli commented Sep 12, 2013

Sorry to post here, this is not an issue but a question. I cannot leave a comment in your post : http://misheska.com/blog/2013/06/23/getting-started-writing-chef-cookbooks-the-berkshelf-way-part2/

Firstly, thanks for your great guide of Chef and Berkshelf. It's fantastic!

Only question for me is how you will manage the configuration for production server. e.g. how to configure the 'server_root_password' for production?

Do you need other chef-repo to manage data_bags, roles, environments etc. if we use hosted-chef or private chef server to manage servers?

If such repository is required, how to use Berkshelf and vagrant to test? I think Berkshelf plugin is not designed for this scenario.

Cheers

misheska pushed a commit that referenced this issue Dec 29, 2013
@misheska
Copy link
Owner

misheska commented Jan 5, 2014

I don't have a concrete example yet, but a production-worthy approach would be to use chef-vault to manage your secrets, per Seth Vargo at Chef.

@misheska
Copy link
Owner

misheska commented Jan 5, 2014

For a concrete example, this blog series on "Building Security with Chef" seems helpful:
http://www.markerbench.com/blog/archives/

@wbingli
Copy link
Author

wbingli commented Apr 1, 2014

Thanks,Mischa

Other question is about how to manage data_bags, roles, environments in Chef. So normally will you create other chef repository for them?

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

2 participants