-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Definition/use of servername
problematic
#127
Comments
Having remembered that ansible's "truthy" is not very intuitive I had a play - what I mean is that I think the templating would be better as: {% if ood_servername is defined and ood_servername %}
ServerName {{ servername }}
{% endif %} That way you can explicitly set |
Thanks for the reminder. Templates are being deprecated in #128. At some point we're going to stop supporting them and folks should just use the To the variable, are you saying the default should actually be null/empty and not |
Re. templates - I think I am using the portal generator, at least I think I see it running in the ansible - isn't my first link the template the portal generator uses?? If not, how would I set Re. the variable. I have no familiarity with name-based virtual hosting so I don't know if the default of |
(firstly, thanks for OOD and this role!)
The definition and use of
servername
is a bit problematic when NOT accessing the OOD node by IP, i.e so we don't want name-based virtual hosting:localhost
)ServerName
directive (?) ifservername
is defined.Firstly, I think the role var should be e.g.
ood_servername
to make it more obvious what it's setting, could refer to loads of things and at least that'd let you look up the OOD docs.Secondly, I think the templating of
SeverName
should be conditional on it being both defined AND truth-y. The problem is that with more complicated inventory setups it can get impossible to un-define the variable again. I can give a specific example but it'll seem odd but I think in general having to have variables undefined to get specific behaviour is problematic.The text was updated successfully, but these errors were encountered: