- From: Miguel Cabeça <
>
- To:
- Subject: [chef] How to Proxy Chef Server with Apache, simpler setup...
- Date: Mon, 28 Jun 2010 18:53:02 +0100
Hi all,
I have a somewhat simpler apache setup than the one featured on the Wiki. It
has the advantage of requiring only the default https port for both API and
WebUI access.
mod_rewrite points to the right merb instance based on the existence of the
X-Chef-Version header presented by API clients.
To keep things simple, the merb instances serves all content. Apache just
proxies it all without serving public content.
Do you think it is ok to edit the wiki page with this example?
Best Regards
Miguel Cabeça
<VirtualHost *:443>
ServerName server_fqdn
DocumentRoot /var/www
LogLevel info
ErrorLog /var/log/apache2/chef_server-error.log
CustomLog /var/log/apache2/chef_server-access.log combined
SSLEngine On
SSLCertificateFile /etc/chef/certificates/server_fqdn.pem
SSLCertificateKeyFile /etc/chef/certificates/server_fqdn.pem
ProxyRequests Off
<Proxy *>
Order deny,allow
Allow from all
</Proxy>
RequestHeader set X_FORWARDED_PROTO 'https'
RewriteEngine on
RewriteCond %{HTTP:X-Chef-Version} .
RewriteRule ^/(.*)
http://localhost:4000/$1 [P]
RewriteRule ^/(.*)
http://localhost:4040/$1 [P]
</VirtualHost>
- [chef] How to Proxy Chef Server with Apache, simpler setup..., Miguel Cabeça, 06/28/2010
Archive powered by MHonArc 2.6.16.