Skip to content
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

What should we do with ServerName value in /etc/httpd/conf.d/tendrl.conf? #217

Open
mbukatov opened this issue Jun 23, 2017 · 2 comments
Open
Assignees
Labels

Comments

@mbukatov
Copy link
Contributor

Right now, we have a ServerName defined with the following default value along with this comment in /etc/httpd/conf.d/tendrl.conf:

<VirtualHost *:80>
  # Adjust the ServerName directive to reflect the FQDN for your host. Add
  # additional ServerAlias directives if required.
  ServerName tendrl

Could we check this again while keeping the fact that this is the default configuration provided by tendrl-api-httpd package (required for both api and web interface) in mind and chose one of:

  • dropping the ServerName completely (it's optional), using automatic deduction instead
  • updating the documentation here to reflect changes needed
  • keeping some default value, while not asking admin to change it neither in the docs in the comment in the file itself

I'm not sure which option would make most sense in our case, but it could be a bit misleading that on one hand our rpm installation docs doesn't mention this, and on the other hand in the default config file, we have a suggestion to change the value.

Affected versions

tendrl-api-httpd-1.4.2-1.el7.centos.noarch

@r0h4n
Copy link
Contributor

r0h4n commented Aug 8, 2017

@anivargi please respond to this

@mbukatov
Copy link
Contributor Author

This should be addressed along with Tendrl/tendrl-ansible#30 (SSL setup), so that there are no error prone unnecessary differences between http and https setup.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants