leap_platform.git - [leap

Age	Commit message (Collapse)	Author
2013-03-14	remove apache ssl proxy in preparation of replacing it with a stunnel setup	Micah Anderson
	This presents us with an interesting problem of deprecation. We need to manage the removal of something that we previously installed in any released code. How long we carry the puppet code that removes raises some interesting questions: do we require that someone who deployed version 1 (where the apache ssl proxy was deployed) of the platform upgrade first to version 2 (where we remove the apache ssl proxy) before they upgrade to version 3 (where the apache ssl proxy removal is no longer present) -- or do we allow people to skip versions?
2013-01-29	eliminate dynamic lookup deprecation warnings for site_couchdb::apache_ssl_proxy	Micah Anderson

2012-12-10	couchdb: use x509 module to deploy certs (fixes #1063)	varac

2012-12-04	remove no longer needed removal of the ports.conf file	Micah Anderson

2012-12-04	alphabetize the apache modules	Micah Anderson

2012-12-04	Stop the [warn] NameVirtualHost *:443 has no VirtualHosts errors	Micah Anderson
	When we include apache::ssl it ships the ssl.conf file which sets up the NameVirtualHost *:443, so we just do what that class does fixes: https://leap.se/code/issues/944
2012-11-08	= true	varac

2012-11-03	added apache_ssl_proxy.pp	varac