Hello Chefs!
I just pushed version 0.1.0 of the httpd cookbook, which you can find here:
https://github.com/opscode-cookbooks/httpd
I'm looking for feedback and initial testers, to help shake the bugs
out ahead of pushing a 1.0.0.
It's meant to be a "shining cookbook on the hill" that people can
reference as an example for creating highly re-usable cross platform
cookbooks.
Cross-platform cookbooks have been a huge source of frustration for a
long time now... Hopefully the design pattern represented here can
lead us out of the darkness.
Features -
* Tested on Debian 7, Ubuntu 12.04 and 14.04, Centos5, Centos6, and Centos7
* 2.2 and 2.4 support where appropriate
* Supports multiple Apache instances on the same machine
* Platform native idioms: no more "ubuntufying" rhel distros. (selinux
should work!)
* Modularity. httpd_config and httpd_module are used to implement httpd_service
* No recipes! This cookbooks is meant to provide primitives... an
extension of Chef.
* Platform providers: resource patterns are self contained for extensibilty
* Init system extensibility: subclassing for sysvinit vs systemd, etc
* Full test coverage: developed from the ground up as a piece of Test
Driven Infrastructure: 28 test-kitchen runs and 1936 specs
Known issues:
* The README needs a lot of love
* The primitives may be a bit *too* primitive.. httpd_service only
loads enough modules to get itself running. Users may expect more
* Needs a roadmap
Let me know what you think!
-s
Archive powered by MHonArc 2.6.16.