了解opsworks和定制食谱共同努力 [英] understand how opsworks and custom cookbooks work together

问题描述

我有我的opsworks和应用程序的部署精（蛋糕PHP）栈。

I have my stack on opsworks and app is deploying fine (cake php).

现在我必须配置一些像文件模式，PHP版本，等等等等...我阅读有关这一点，但不知道到底是什么最好的办法做到这一点。

Now I have to configure some things like chmod, php versions, etc etc... I'm reading about this but don't know exactly whats the best way to do this.

问题1 - 我应该这样做自定义部署JSON或通过定制的食谱

Question 1 - Should I do this with custom deploy JSON or via custom cookbooks?

问题2 - 请告诉我正确的方式使用自定义的食谱工作？叉原来AWS存储库，更新配方，然后使用它在我的筹码？

Question 2 - Whats the correctly way to work with custom cookbooks? Fork original AWS repositories, update recipes and then use it in my stack?

推荐答案

取决于你想要什么来实现的，你可以实现很多东西，如：

depends on what you would like to achieve, you may implement many things, such as:

1. 在一个配方，这是在只调用一次 chef-客户端运行。
2. 在一个轻量资源提供商，它支持通知和可以被调用零次或多次。
3. 一个定义，该可用资源集合之前，可以调用零次或多次。

1. a recipe, which is invoked only once during a chef-client run.
2. a lightweight resource provider, which supports notifies and can be invoked zero or more times.
3. a definition, which is available before resource collection and can be invoked zero or more times.

关于第二个问题，第一个结算 berkshelf - 一本食谱经理。 我建议派生一个项目只有当项目是死了，否则我会考虑作出贡献已经实施的项目，所以每个人都会从中受益;你可以随时编写自己的包装食谱，您也可以参考厨师包装食谱最佳实践的。

for your second question, first checkout berkshelf -- a cookbook manager. i would suggest forking a project only if the project is dead, otherwise i would consider to contribute to already implemented project so everybody will benefit from it; and you can always write your own wrapper cookbook, you can also refer to Chef wrapper cookbook best practices.

这篇关于了解opsworks和定制食谱共同努力的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！