Description

Problem: I don't use a subdomain, so HOSTNAME in the code becomes just the TLD of my domain and causes several issues (primarily with _monitored_files_checksums). I think requiring OVERRIDE_HOSTNAME adds unnecessary complexity and isn't easy to figure out for new users without spending some time.

Solution: Centralize the collection of the HOSTNAME and DOMAINAME so that it's predictable and uniform across the various scripts (using the helper). Ensure it supports the various configurations users can have (both subdomain and without subdomain, override and no override).

Also, DOMAINNAME as an env is supported for overriding SRS_DOMAINNAME, but not any other logic. Now that it's all using the same logic, specifying DOMAINNAME should override anywhere it shows up and is used in the code.

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Improvement (non-breaking change that does improve existing functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation (README.md or the documentation under docs/)
• If necessary I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes