Hey P.J., I looked into this and chef-server.rb isn't being ignored. It looks like either we have a bug or our docs are wrong. Instead of setting nginx['non_ssl_port'] = nil, set it to nginx['non_ssl_port'] = false and then run chef-server-ctl reconfigure. nil currently causes the defaults to be left in place (or put back into place if they had been removed). I'll follow up and either get a bug filed or the docs updated, but this should move you forward. And just to give you more information than you likely need, chef configures itself with chef (it uses chef-solo). The cookbooks that do this are installed by the omnibus installer to /opt/chef-server/embedded/cookbooks/chef-server. You can always look there and read them to see the default values that will be applied. You can view the omnibus-chef-server repo and see how everything that creates the installer package is put together: https://github.com/opscode/omnibus-chef-server. This conforms to omnibus packaging conventions, so the above mentioned cookbooks are in files/chef-server-cookbooks/chef-server in that repo. Since we're talking about nginx here, the cookbooks will render the nginx config to /var/opt/chef-server/nginx/etc/ so you can always look there to see what nginx config chef is using. It's still recommended that you make changes by modifying /etc/chef-server/chef-server.rb. Sorry for our mistake and the confusion it caused you. Let me know if that doesn't solve your issue. As I said, I'll follow up to make sure either the docs are updated or that we fix a bug that causes nil not to work (I suspect it's our docs that are wrong, however). Thanks, Mark Mzyk Chef Software Engineer " type="cite"> |
Archive powered by MHonArc 2.6.16.