| Age | Commit message (Collapse) | Author |
|---|
|
this already exists in class site_stunnel::setup which is instantiated in this
class
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
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?
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
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
|
|
https://leap.se/code/issues/994
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
don't start on port 80/443
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
