Updated README.md to reflect the correct 'DEFAULT_DOMAIN' value. #695
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There is an extremely important bit of information in the Docker .env section that's surprisingly missing.
You see, the most common use case for this app is to be able to host it in a private server in the cloud, front-ended by a reverse proxy. And when we add TLS termination into the MIX as well, it becomes all the more important to advise the general audience that the 'DEFAULT_Domain' is supposed to contain the FQDN value (inclusive of the host portion) and not just the domain portion. If only the domain portion is included, obvious strange behaviours tend to occur, including a scenario where an NGINX reverse proxy redirects any kutt-owned subdomains to a root domain hosted on the same server if the 'DEFAULT_DOMAIN'.